Send monthly rent and sales market updates to Slack with Rentcast and Supabase
Ready for 3.0What this workflow does
This workflow has 20 nodes and runs on a schedule (every month). Along the way it connects Supabase and Slack. It also calls api.rentcast.io and voffipplerpdeedrexvf.supabase.co over HTTP.
How it runs
Trigger: On a schedule (every month).
- Set Zipcode Parameter (Edit Fields (Set)): sets 1 field: zipcode
- Fetch Rentals from Supabase (Supabase): get many
- Fetch Sales from Supabase (Supabase): get many
- Merge: merges the data from its input branches
- Aggregate: combines items into one
- If: checks a condition and branches into true / false
- Analyze Empty Data Response (Code): runs custom JavaScript code
- Fetch Market Data (HTTP Request): calls api.rentcast.io
- If: checks a condition and branches into true / false
- Upsert Rentals to Supabase (HTTP Request): calls voffipplerpdeedrexvf.supabase.co (POST)
…plus 9 more steps. See the full node list below.
Services it uses
HTTP calls to: api.rentcast.io, voffipplerpdeedrexvf.supabase.co
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 (9)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HTTP Request
n8n-nodes-base.httpRequest - Edit Fields (Set)
n8n-nodes-base.set - Supabase
n8n-nodes-base.supabase - Merge
n8n-nodes-base.merge - If
n8n-nodes-base.if - Aggregate
n8n-nodes-base.aggregate - Code
n8n-nodes-base.code - Slack
n8n-nodes-base.slack
From the author
Quick overview Youtube Video: https://youtu.be/zJlncb1T074 This workflow runs monthly, checks Supabase for up-to-date real estate market records for a configured ZIP code, and either reports existing month-over-month rent and sale trends or fetches fresh…