Weekday review monitor with critical-review Slack alerts

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.