Triage stale property listings with Google Sheets, Gemini, and Slack
Ready for 3.0What this workflow does
This workflow has 11 nodes and runs on a schedule (cron 0 8 * * *) (plus 1 other trigger). Along the way it connects Slack and Google Sheets. It also calls generativelanguage.googleapis.com over HTTP.
How it runs
Trigger: On a schedule (cron 0 8 * * *) (plus 1 other trigger).
- Read Listings from Sheets (Google Sheets): uses Google Sheets
- Post Error to Slack (Slack): uses Slack
- Compute Listing Metrics (Code): runs custom JavaScript code
- Update Trend Snapshot in Sheets (Google Sheets): append or update
- Filter: keeps only the items that match a condition
- Post to Gemini API (HTTP Request): calls generativelanguage.googleapis.com (POST)
- Set AI Response Field (Edit Fields (Set)): sets 1 field: ai
- Notify via Slack (Slack): uses Slack
- Update Listings Status in Sheets (Google Sheets): update
Services it uses
HTTP calls to: generativelanguage.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 (8)
- Error Trigger
n8n-nodes-base.errorTrigger - Slack
n8n-nodes-base.slack - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Google Sheets
n8n-nodes-base.googleSheets - Code
n8n-nodes-base.code - Filter
n8n-nodes-base.filter - HTTP Request
n8n-nodes-base.httpRequest - Edit Fields (Set)
n8n-nodes-base.set
From the author
Quick overview Demo Link: https://www.linkedin.com/feed/update/urn:li:activity:7503832069614215168/ This workflow runs daily to scan property listings in Google Sheets, detect stale or low-performing leads using portfolio benchmarks, generate a diagnosis with…