This workflow follows the HTTP Request → Slack recipe pattern — see all workflows that pair these two integrations.
The workflow JSON
Copy or download the full n8n JSON below. Paste it into a new n8n workflow, add your credentials, activate. Full import guide →
{
"name": "01.02 Automated Budget vs. Actuals Cloud Cost Monitoring",
"nodes": [
{
"parameters": {
"path": "webhook-01-02"
},
"id": "67dbd6f0-8bc7-4f05-8a88-1664f1bd3cf4",
"name": "Webhook Trigger",
"type": "n8n-nodes-base.webhook",
"typeVersion": 1,
"position": [
200,
300
]
},
{
"parameters": {
"content": "## Automated Budget vs. Actuals Cloud Cost Monitoring\n\n**The Problem:**\nCloud spend often spirals out of control before FinOps can catch it. Manual comparison between AWS bills and NetSuite budgets is too slow for agile cost management.",
"height": 200,
"width": 600
},
"id": "642d2fb4-32bb-443c-833c-87289bcb94c4",
"name": "Sticky Note",
"type": "n8n-nodes-base.stickyNote",
"typeVersion": 1,
"position": [
200,
50
]
},
{
"parameters": {},
"id": "45f1d862-dab8-4bb4-a0e4-1b7125ddaa4e",
"name": "AWS Cost Explorer",
"type": "n8n-nodes-base.aws",
"typeVersion": 1,
"position": [
450,
300
]
},
{
"parameters": {},
"id": "a954f538-06e3-4fbe-8adc-7dcbab461a98",
"name": "NetSuite",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 1,
"position": [
700,
300
]
},
{
"parameters": {},
"id": "96282a10-ac13-4c32-871a-c03c545e9cb5",
"name": "Jira",
"type": "n8n-nodes-base.jira",
"typeVersion": 1,
"position": [
950,
300
]
},
{
"parameters": {},
"id": "43810b9d-e186-457e-8697-94a43af9ece6",
"name": "Slack",
"type": "n8n-nodes-base.slack",
"typeVersion": 1,
"position": [
1200,
300
]
}
],
"connections": {
"Webhook Trigger": {
"main": [
[
{
"node": "AWS Cost Explorer",
"type": "main",
"index": 0
}
]
]
},
"AWS Cost Explorer": {
"main": [
[
{
"node": "NetSuite",
"type": "main",
"index": 0
}
]
]
},
"NetSuite": {
"main": [
[
{
"node": "Jira",
"type": "main",
"index": 0
}
]
]
},
"Jira": {
"main": [
[
{
"node": "Slack",
"type": "main",
"index": 0
}
]
]
}
},
"active": false,
"settings": {},
"versionId": "f67c462a-a64d-41c1-a564-6dcaf7db0c18"
}
For the full experience including quality scoring and batch install features for each workflow upgrade to Pro
About this workflow
01.02 Automated Budget vs. Actuals Cloud Cost Monitoring. Uses aws, httpRequest, jira, slack. Webhook trigger; 6 nodes.
Source: https://github.com/avuzmal/n8n.automation/blob/main/workflows/01_02_automated_budget_vs_actuals_cloud_cost_monitoring.json — original creator credit. Request a take-down →
Related workflows
Workflows that share integrations, category, or trigger type with this one. All free to copy and import.
Are you tired of the repetitive dance between git push, creating a pull request in GitHub, updating the corresponding task in JIRA, and then manually notifying your team in Slack, or Notion?
This workflow is an AI-powered style look transfer and quality control pipeline designed for VFX and editorial production. It transforms a new shot brief and a hero reference image into multiple style
HR teams, IT Operations, and System Administrators managing employee onboarding at scale. It’s perfect if you use Odoo 18 to trigger account requests and need Redmine + GitLab accounts created instant
This workflow is a complete, production-ready solution for recovering abandoned carts in Shopify stores using a multi-channel, multi-touch approach. It automates personalized follow-ups via Email, SMS
Backbrief: transcripts (Zoom webhook -> Slack + vault). Uses httpRequest, slack. Webhook trigger; 52 nodes.