When should you use it?
- You sell reputation or automation services locally
- You want a timely reason to call
- You can scrape review data legitimately
Not for: Spamming owners with automated messages; Scraping that breaks a site's terms
What do you need, and what do you get?
You need
- Review data source
- Filters: rating threshold, review score, no owner reply
- Delivery channel
You get
- List of matching businesses
- Call script per business
How does it work, step by step?
- Set the filtersHigh overall rating, a fresh low review, and no owner response.
- Collect reviewsPull recent reviews through a data provider you are allowed to use.
- Match and rankKeep businesses that meet all three conditions.
- Draft the scriptWrite an opening that references the review respectfully.
- DeliverSend to email or Slack for a person to call.
The prompt
Our own prompt, inspired by Gary Xia and written to work in n8n and ChatGPT. Values in lime are placeholders.
From the review data I provide, find businesses with an overall rating above 4.0 that got a rating at or below three in the last [7] days with no owner response. For each, list the business, the review date, a one-line paraphrase of the complaint and a short phone opener offering help with a reply. Do not contact anyone. Send the list to my Slack.
Inspired by Gary Xia: CommunityPulse: Automating Lead Gen for AI Agencies with n8n Agents and Bright Data. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Quoting a customer's complaint back to an owner can feel intrusive; keep it brief and helpful.
- Check scraping terms for every source.
Our take
The filter logic is the clever bit: three cheap conditions that turn raw reviews into a reason to call. A free damage-control offer is a sensible opener. Gary's three conditions, a rating above 4.0, a fresh review of 3 or lower, and no reply from the owner, are cheap to check and point to a business that cares about its reputation but has not responded yet. That gives an agency a timely, relevant reason to get in touch. Collect review data only through a provider whose terms allow it, and check those terms for every source. The opening message should reference the review briefly and offer help, not quote the complaint back at length, which can feel intrusive. Send the alerts to email or Slack for a person to follow up; automated messages to owners would turn a useful signal into spam. Keep a do-not-contact list, and never suggest buying reviews as a fix.
Where the time goes back: Instead of cold lists, you get a short list of owners with a fresh, specific problem.
FAQ
Why rated above 4.0?
Why no owner reply?
Source and credit
Inspired by Gary Xia. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- CommunityPulse: Automating Lead Gen for AI Agencies with n8n Agents and Bright Data
- Creator
- Gary Xia
- Published on
- DEV Community
- Original date
- Sep 1, 2025
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- n8n
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.