Automation library · Alerts and monitoring

AWS Azure GCP multi-cloud cost monitoring & alerts

Started by a clock, and works across Email, Slack and WhatsApp. 11 steps, 1 branch: a working afternoon to understand properly.

Medium

11 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
3Services it connects to

The flow

Starts it 1Logic 4Service 6

The steps in the order they run, from what starts it.

  1. 1Cron TriggerCronStarts it
  2. 2AWS Billing FetchHttp RequestService
  3. 3Azure Billing FetchHttp RequestService
  4. 4GCP Billing FetchHttp RequestService
  5. 5Data ParserCodeLogic
  6. 6Cost Spike DetectorCodeLogic
  7. 7Owner IdentifierIfLogic
  8. 8Auto-Tag ResourceCodeLogic
  9. 9Alert Sender On SlackSlackService
  10. 10Alert Sender On WhatsAppWhats AppService
  11. 11Alert Sender On EmailEmail SendService

How it's built

Starts on
A clock
Steps
11, with 1 branch
Size
Medium: a working afternoon
Connects to
Email, Slack, WhatsApp
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Email, Slack and WhatsApp accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 11 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 11 steps before you point it at anything that matters.