AWS Azure GCP multi-cloud cost monitoring & alerts for budget control
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Cron. 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 11 nodes and runs on a schedule (legacy Cron node). Along the way it connects WhatsApp Business Cloud and Slack. It also calls ce.us-east-1.amazonaws.com over HTTP.
How it runs
Trigger: On a schedule (legacy Cron node).
- AWS Billing Fetch (HTTP Request): calls ce.us-east-1.amazonaws.com (POST)
- Azure Billing Fetch (HTTP Request): calls an HTTP API (POST)
- GCP Billing Fetch (HTTP Request): calls an HTTP API
- Data Parser (Code): runs custom JavaScript code
- Cost Spike Detector (Code): runs custom JavaScript code
- Owner Identifier (If): checks a condition and branches into true / false
- Auto-Tag Resource (Code): runs custom JavaScript code
- Alert Sender On Slack (Slack): uses Slack
- Alert Sender On WhatsApp (WhatsApp Business Cloud): send
- Alert Sender On Email (Send Email): sends an email over SMTP
Services it uses
HTTP calls to: ce.us-east-1.amazonaws.com
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Cron in Cron Trigger: replace with Schedule Trigger.
| Removed in 3.0 | Replace with |
|---|---|
| Cron Cron Trigger | Schedule Trigger |
Nodes used (7)
- Cron
n8n-nodes-base.cron - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Send Email
n8n-nodes-base.emailSend - WhatsApp Business Cloud
n8n-nodes-base.whatsApp - Slack
n8n-nodes-base.slack
From the author
This automated n8n workflow tracks hourly cloud spending across AWS, Azure, and GCP. It detects cost spikes or budget overruns in real time, tags affected resources, and sends alerts via email, WhatsApp, or Slack. This ensures proactive cost management and…