Send outdoor booking weather risk alerts with Airtable, Open-Meteo, Slack and WhatsApp
Ready for 3.0What this workflow does
This workflow has 17 nodes and runs on a schedule (every day at 06:00). Along the way it connects Airtable, Slack and WhatsApp Business Cloud. It also calls geocoding-api.open-meteo.com and api.open-meteo.com over HTTP.
How it runs
Trigger: On a schedule (every day at 06:00).
- Prepare Configuration Settings (Edit Fields (Set)): sets 8 fields: airtable_base_id, bookings_table_name, whatsapp_phone_number_id…
- Retrieve Outdoor Bookings (Airtable): search
- Filter Upcoming Bookings (Code): runs custom JavaScript code
- Geocode Booking Locations (HTTP Request): calls geocoding-api.open-meteo.com
- Retrieve Weather Forecast (HTTP Request): calls api.open-meteo.com
- Calculate Weather Risk (Code): runs custom JavaScript code
- Check for Any Weather Risk (If): checks a condition and branches into true / false
- Evaluate Severe Weather Risk (If): checks a condition and branches into true / false
- Check Customer Notification Status (If): checks a condition and branches into true / false
- Alert Owner - Moderate Risk (Slack): uses Slack
…plus 6 more steps. See the full node list below.
Services it uses
HTTP calls to: geocoding-api.open-meteo.com, api.open-meteo.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)
- Airtable
n8n-nodes-base.airtable - Slack
n8n-nodes-base.slack - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if - WhatsApp Business Cloud
n8n-nodes-base.whatsApp
From the author
Quick overview This workflow runs daily to check upcoming confirmed outdoor bookings in Airtable, fetches location-based forecasts from Open-Meteo, scores weather risk, and sends Slack and WhatsApp notifications for moderate or severe conditions while…