Monitor ride surge events and analyze ride errors with Sheets, Slack and Gemini
Ready for 3.0What this workflow does
This AI workflow has 15 nodes and runs manually, when you click “Execute workflow”. Along the way it connects Slack, Google Gemini, HTTP Request and Google Sheets.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Fetch Ride Events (Google Sheets): uses Google Sheets
- Process Each Ride Event (Loop Over Items (Split in Batches)): loops over the items in batches
- Control Processing Delay (Wait): waits 3 seconds
- Split Event vs Error Flow (Switch): routes items into 2 branches
- Decision: Detect Surge Pricing & Delay (If): checks a condition and branches into true / false
- Structure Error Context Data (Edit Fields (Set)): sets or maps fields
- Alert: Send Surge Slack Notification (Slack): uses Slack
- Record Normal Ride Event (Edit Fields (Set)): sets 4 fields: log_type, log_city, log_status…
- Diagnose Issue & Recommend Actions (Google Gemini): uses Google Gemini, with 2 tools (Get Real-Time Traffic Data, Get Real-Time Weather Data)
- Record Surge Alert Event (Edit Fields (Set)): sets 5 fields: log_type, log_city, log_ride_price…
…plus 2 more steps. See the full node list below.
Services it uses
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.
- Still check Always Output Data on multi-output nodes (If/Switch) now adds an empty item only when every output is empty (Split Event vs Error Flow).
Nodes used (11)
- Slack
n8n-nodes-base.slack - Manual Trigger
n8n-nodes-base.manualTrigger - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Wait
n8n-nodes-base.wait - Switch
n8n-nodes-base.switch - If
n8n-nodes-base.if - Edit Fields (Set)
n8n-nodes-base.set - Google Gemini
@n8n/n8n-nodes-langchain.googleGemini - Http Request Tool
n8n-nodes-base.httpRequestTool - Code
n8n-nodes-base.code - Google Sheets
n8n-nodes-base.googleSheets
From the author
Quick overview This workflow pulls ride events and error records from Google Sheets, detects surge pricing and long waits, and notifies via Slack. For error records, it uses Google Gemini with real-time traffic and weather API lookups to diagnose the issue…