Weekday Review Monitor: G2, Capterra, Trustpilot Alerts in Slack

Every weekday at 9am in my local timezone, monitor a list of public review pages for my product and key competitors on G2, Capterra, and Trustpilot, and post a Slack message for each genuinely new review. Critical reviews (one or two stars) get an @-mention to my support lead.

Trigger: a cron schedule that fires Monday through Friday at 9am local time. Skip Saturday and Sunday entirely.

Configuration lives in Google Sheets. Use Get Values on a tab called 'sources' that has columns for product or competitor name, source site (G2, Capterra, or Trustpilot), and review page URL. One row per page. Use Get Values again on a tab called 'log' that holds every review the workflow has already reported, with columns for review ID, date seen, source site, product or competitor name, rating, reviewer name or role, summary, sentiment, and link.

For each URL in the 'sources' tab, fetch the page with Proxy Scrape's Fetch a Web Page operation. Use the stealth proxy tier for G2 and Capterra because Cloudflare will block weaker tiers. Trustpilot works on the default tier. Return markdown so reviews are easy to parse.

Parse the returned content and pull out every review posted in the last 24 hours. For each review, extract: a stable review ID (use the review's anchor or URL fragment when available, otherwise hash source plus product plus posted date plus reviewer plus rating), the posted date, source site, product or competitor name, star rating, reviewer name or role, the full body text, and a direct link to the review.

Dedupe against the 'log' tab. Drop any review whose ID already appears there. Only genuinely new reviews continue.

For each new review, write a one-sentence summary of what the reviewer is actually saying and classify sentiment as positive, mixed, or negative. Pick one verbatim pull quote (one or two sentences) from the review body that best captures the reviewer's main point. Keep the summary grounded in the review body, do not invent details.

Append every new review to the 'log' tab using Append Values. One row per review with date seen, source site, product or competitor name, rating, reviewer, the one-sentence summary, sentiment, and link. This is what prevents duplicate posts tomorrow.

For each new review, send a Slack message to the configured channel using Send a Message. Each message should include:

A header line with the product or competitor name, source site, and star rating (e.g. ⭐⭐ on G2 for Acme).
The one-sentence summary.
The verbatim pull quote, formatted as a Slack blockquote.
A link to the original review.

If the review is one or two stars AND it is about my own product (not a competitor), prepend an @-mention to the configured support lead's Slack user ID and add a 'needs response' tag at the end of the message. Treat this as the critical path: support should always see these first.

If no genuinely new reviews are found across any source on a given morning, skip the Slack post entirely. Do not send an 'all quiet today' message.

Make the following easy to change without editing the agent instructions: the Google Sheet ID and tab names, the Slack channel, the support lead's Slack user ID, the rating threshold for critical reviews, which product name in the sources tab counts as 'my own product', and the run time.

Additional information

What does this prompt do?

Watches your product's and your competitors' public review pages each weekday morning and pulls out anything posted in the last 24 hours.
Logs every new review to a Google Sheet (date, source, rating, reviewer, summary, sentiment) so the same review never gets posted twice.
Posts a Slack message for each new review with the rating, a one-sentence summary, the verbatim pull quote, and a link to the original.
Flags one and two star reviews with an @-mention to your support lead and tags them 'needs response' so nothing critical sits unanswered.

What do I need to use this?

A Proxy Scrape account so the workflow can read G2 and Capterra pages even when Cloudflare blocks normal traffic.
A Google Sheet with one tab listing the product and competitor review URLs you want to watch, plus a tab the workflow can append a running log to.
A Slack workspace, the channel where the morning posts should land, and the user ID of whoever should be tagged on critical reviews.

How can I customize it?

Add or drop products and competitors by editing the URL list in your Google Sheet, no workflow changes needed.
Change what counts as critical from one or two stars to a different threshold, or switch the support lead who gets tagged.
Move the run time, the Slack channel, or the rating fields the digest highlights without touching the agent.

Frequently asked questions

Will this work on G2 and Capterra, which usually block scrapers?

Yes. Proxy Scrape's stealth tier handles Cloudflare on G2 and the same approach works for Capterra. Trustpilot reads on the standard tier.

Can I track my own product alongside competitors?

Yes, that is the point. Mix your own review URLs in with competitor URLs in the same Google Sheet and the workflow treats them the same way.

Will the same review ever post twice?

No. Every review the workflow finds is logged to Google Sheets and checked against that log before anything goes to Slack.

What happens on quiet days with no new reviews?

The workflow stays silent. If nothing new lands, it skips the Slack post for the day instead of pinging your team with an empty message.

How are critical reviews handled differently?

Any review at one or two stars gets an @-mention to the support lead you choose and a 'needs response' tag in the Slack message, so the worst feedback is impossible to miss.