The flow
Starts it 1Logic 10Service 9
The steps in the order they run, from what starts it.
- 1Monthly TriggerSchedule triggerStarts it
- 2Set Zipcode ParameterSetLogic
- 3Fetch Rentals from SupabaseSupabaseService
- 4Fetch Sales from SupabaseSupabaseService
- 5Merge Supabase ResultsMergeLogic
- 6Aggregate Market DataAggregateLogic
- 7If Data ExistsIfLogic
- 8Analyze Empty Data ResponseCodeLogic
- 9Fetch Market DataHttp RequestService
- 10If Data MissingIfLogic
- 11Upsert Rentals to SupabaseHttp RequestService
- 12Upsert Sales to SupabaseHttp RequestService
- 13Notify Missing Data to SlackSlackService
- 14Notify Admin of ErrorSlackService
- 15Merge Market UpdatesMergeLogic
- 16Aggregate Upsert StatusAggregateLogic
- 17Check Upsert SuccessCodeLogic
- 18If Upsert SuccessfulIfLogic
- 19Post Success to SlackSlackService
- 20Post Error to SlackSlackService
How it's built
- Starts on
- A clock
- Steps
- 20, with 3 branches
- Size
- Medium: a working afternoon
- Connects to
- Slack, Supabase
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Slack and Supabase accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 20 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 20 steps before you point it at anything that matters.