The flow
Starts it 1Logic 6Service 10
The steps in the order they run, from what starts it.
- 1Check Weather Daily at 6amSchedule triggerStarts it
- 2Prepare Configuration SettingsSetLogic
- 3Retrieve Outdoor BookingsAirtableService
- 4Filter Upcoming BookingsCodeLogic
- 5Geocode Booking LocationsHttp RequestService
- 6Retrieve Weather ForecastHttp RequestService
- 7Calculate Weather RiskCodeLogic
- 8Check for Any Weather RiskIfLogic
- 9Evaluate Severe Weather RiskIfLogic
- 10Check Customer Notification StatusIfLogic
- 11Alert Owner - Moderate RiskSlackService
- 12Re-Alert Owner (Severe Risk)SlackService
- 13Inform Customer (Weather Risk)Whats AppService
- 14Update Moderate Risk RecordAirtableService
- 15Update Severe Risk RecordAirtableService
- 16Alert Owner (Severe Risk)SlackService
- 17Log Customer NotificationAirtableService
How it's built
- Starts on
- A clock
- Steps
- 17, with 3 branches
- Size
- Medium: a working afternoon
- Connects to
- Airtable, Slack, WhatsApp
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Airtable, Slack and WhatsApp 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. 17 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 17 steps before you point it at anything that matters.