Send monthly rent and sales market updates to Slack with Rentcast and Supabase
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
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
What it does
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 market stats from the Rentcast API, upserts them into Supabase, and posts to Slack. How it works 1. Runs on a monthly schedule and sets the target ZIP code to analyze. 2. Queries Supabase for rental and sales market records for that ZIP code that are older than the start of the current month. 3. If prior data exists, calculates the last 3 months of average rent and average sale price changes from Supabase history fields and posts a status summary to Slack (or alerts if comparisons are not possible). 4. If no up-to-date data exists, requests the latest market statistics from the Rentcast markets API for the same ZIP code. 5. Upserts the returned rental and sales metrics (including history) into Supabase tables for marketrentals and marketsales. 6. Computes month-over-month changes from the newly fetched history and posts the formatted market update to Slack (or sends an error alert if insufficient data is returned). Setup 1. Create/connect Supabase credentials and ensure the marketrentals and marketsales tables exist with columns that match the fields being written (for example zipcode, lastupdateddate, and historyrentals/historysales). 2. Add your Rentcast API key and update the HTTP request header (X-Api-Key) and any query parameters (ZIP code, historyRange) as needed. 3. Connect Slack OAuth credentials and set the target channel for all Slack messages. 4. Update the ZIP code value and adjust the monthly schedule timing to match your reporting cadence.