Detect cloud cost spikes with Google Sheets, Slack, Gmail, and Jira
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 workflow has 11 nodes and runs on a schedule (every day at 08:00). Along the way it connects Google Sheets, Jira Software, Slack and Gmail.
How it runs
Trigger: On a schedule (every day at 08:00).
- Fetch Daily Cost (HTTP Request): calls an HTTP API
- Read Cost Baseline (Google Sheets): uses Google Sheets
- Calculate Spike (Code): runs custom JavaScript code
- Valid Data (If): checks a condition and branches into true / false
- Is Spike (If): checks a condition and branches into true / false
- Classify Severity (Edit Fields (Set)): sets 4 fields: severity, severityEmoji, ticketPriority…
- Create Jira Incident (Jira Software): uses Jira Software
- Slack: uses Slack
- Email Finance Summary (Gmail): uses Gmail
- Log Run to Sheet (Google Sheets): append
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 (9)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HTTP Request
n8n-nodes-base.httpRequest - Google Sheets
n8n-nodes-base.googleSheets - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Edit Fields (Set)
n8n-nodes-base.set - Jira Software
n8n-nodes-base.jira - Slack
n8n-nodes-base.slack - Gmail
n8n-nodes-base.gmail
From the author
Quick Overview This workflow runs daily to pull cloud spend from a billing API, compare it to a Google Sheets rolling baseline, and alert on cost spikes by creating a Jira incident, posting to Slack, emailing Finance via Gmail, and logging the run back to…