Monitor restaurant ratings with Google Places, Gemini, Sheets, and Slack
Ready for 3.0What this workflow does
This AI workflow has 14 nodes and runs on a schedule (every day). Along the way it connects Google Sheets, Google Gemini and Slack. It also calls maps.googleapis.com over HTTP.
How it runs
Trigger: On a schedule (every day).
- 📊 Read Restaurant List (Google Sheets): uses Google Sheets
- 🔄 Loop Over Restaurants (Loop Over Items (Split in Batches)): loops over the items in batches
- 🌐 Fetch Live Data (Google Places API) (HTTP Request): calls maps.googleapis.com
- 🧠 Change Detection Engine (Code): runs custom JavaScript code
- 🚦 Alert Worthy? (IF) (If): checks a condition and branches into true / false
- 🤖 AI Diagnosis (Google Gemini) (Google Gemini): uses Google Gemini
- Merge: merges the data from its input branches
- 📡 Alert Routing (Switch) (Switch): routes items into 3 branches
- 🔴 Critical Alert (Slack) (Slack): uses Slack
- 🟡 Watch Alert (Slack) (Slack): uses Slack
…plus 3 more steps. See the full node list below.
Services it uses
HTTP calls to: maps.googleapis.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (10)
- Google Sheets
n8n-nodes-base.googleSheets - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Google Gemini
@n8n/n8n-nodes-langchain.googleGemini - Merge
n8n-nodes-base.merge - Switch
n8n-nodes-base.switch - Slack
n8n-nodes-base.slack - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
What this workflow does Automatically monitors restaurant ratings on Google Places daily, detects meaningful changes, uses Google Gemini AI to diagnose the root cause from real customer reviews, and delivers smart alerts to Slack — categorised as 🔴 Critical,…