Send weekly multi-platform review reports from Apify to Gmail
Needs changesWhat this workflow does
This workflow has 7 nodes and runs on a schedule (cron 0 8 * * 5). Along the way it connects Gmail. It also calls api.apify.com over HTTP.
How it runs
Trigger: On a schedule (cron 0 8 * * 5).
- Post Review Scrape Request (HTTP Request): calls api.apify.com (POST)
- Retrieve Scraped Reviews (HTTP Request): calls an HTTP API (GET)
- Compile Reviews by Business (Code): runs custom JavaScript code
- Consolidate Reports (Item Lists): reshapes item lists (legacy Item Lists node)
- Generate HTML Report (Code): runs custom JavaScript code
- Send Weekly Reputation Email (Gmail): uses Gmail
Services it uses
HTTP calls to: api.apify.com
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Item Lists (legacy) in Consolidate Reports: replace with Split Out, Aggregate, Sort, Limit, Remove Duplicates or Summarize (match the operation used).
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Item Lists (legacy) Consolidate Reports | Split Out, Aggregate, Sort, Limit, Remove Duplicates or Summarize (match the operation used) |
Nodes used (5)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - Item Lists
n8n-nodes-base.itemLists - Gmail
n8n-nodes-base.gmail
From the author
Quick overview This workflow runs every Friday at 8am to scrape the past week’s reviews from Google Maps, Yelp, and TripAdvisor using an Apify Actor, aggregates results by business, and sends a branded HTML reputation report to a client via Gmail. How it…