Monitor multi-city courier weather risk with Open-Meteo, GPT-4o, Gemini and Slack
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.
What this workflow does
This AI workflow has 15 nodes and runs on a schedule (every 6 hours) (plus 1 other trigger). Along the way it connects OpenAI Chat Model, Google Gemini Chat Model and Slack.
How it runs
Trigger: On a schedule (every 6 hours) (plus 1 other trigger).
- City config (Code): runs custom JavaScript code
- Build form city config (Code): runs custom JavaScript code
- Fetch Open-Meteo (HTTP Request): calls an HTTP API
- Score + dedup (Code): runs custom JavaScript code
- Route (Alerts / Errors) (Switch): routes items into 2 branches
- OpenAi — write alerts (Basic LLM Chain): sends a prompt to an LLM, with model: OpenAI Chat Model, Google Gemini Chat Model
- Format Error Msg (Code): runs custom JavaScript code
- Format Alerts & Fallback (Code): runs custom JavaScript code
- Slack: uses Slack
- Slack: uses Slack
…plus 1 more step. See the full node list below.
Services it uses
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 (10)
- OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Basic LLM Chain
@n8n/n8n-nodes-langchain.chainLlm - Google Gemini Chat Model
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - Slack
n8n-nodes-base.slack - Code
n8n-nodes-base.code - n8n Form
n8n-nodes-base.form - Switch
n8n-nodes-base.switch - HTTP Request
n8n-nodes-base.httpRequest - n8n Form Trigger
n8n-nodes-base.formTrigger - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
Quick overview This workflow checks 48-hour forecasts from Open-Meteo for multiple cities on a 6-hour schedule or via an on-demand n8n form, scores conditions against courier-impact thresholds, uses OpenAI (with Google Gemini fallback) to draft Slack-ready…