Real-time oil price crisis detection with Qwq-32b AI and multi-channel alerts
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 20 nodes and runs on a schedule (every minute). Along the way it connects Gmail, Slack, Postgres and OpenRouter Chat Model.
How it runs
Trigger: On a schedule (every minute).
- Workflow Configuration (Edit Fields (Set)): sets 10 fields: oilPriceApiUrl, opecReportsUrl, shippingDataUrl…
- Fetch Oil Price Data (API) (HTTP Request): calls an HTTP API
- Fetch OPEC Reports (HTTP Request): calls an HTTP API
- Fetch Shipping Data (HTTP Request): calls an HTTP API
- Fetch News Feed (HTTP Request): calls an HTTP API
- Merge: merges the data from its input branches
- Data Cleaning & Preprocessing (Code): runs custom JavaScript code
- Statistical Anomaly Detection (Code): runs custom JavaScript code
- AI Trend & Geopolitical Analyzer (AI Agent): runs an AI agent, with model: OpenRouter Chat Model
- Calculate Crisis Risk Score (Code): runs custom JavaScript code
…plus 8 more steps. 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 (11)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Merge
n8n-nodes-base.merge - Code
n8n-nodes-base.code - AI Agent
@n8n/n8n-nodes-langchain.agent - Switch
n8n-nodes-base.switch - Gmail
n8n-nodes-base.gmail - Slack
n8n-nodes-base.slack - Postgres
n8n-nodes-base.postgres - OpenRouter Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenRouter
From the author
How It Works Scheduled runs collect data from oil markets, global shipping movements, news sources, and official reports. The system performs statistical checks to detect anomalies and volatility shifts. An AI-driven geopolitical model evaluates emerging…