Automation library · Alerts and monitoring

Detect cloud cost spikes with Google Sheets and Slack

Started by a clock, and works across Gmail, Google Sheets, Jira and Slack. 11 steps, 2 branches: a working afternoon to understand properly.

Medium

11 stepsMedium: a working afternoon
2Branches: places the flow splits
0Loops or waits
4Services it connects to

The flow

Starts it 1Logic 4Service 6

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

  1. 1Daily ScheduleSchedule triggerStarts it
  2. 2Fetch Daily CostHttp RequestService
  3. 3Read Cost BaselineGoogle SheetsService
  4. 4Calculate SpikeCodeLogic
  5. 5Valid DataIfLogic
  6. 6Is SpikeIfLogic
  7. 7Classify SeveritySetLogic
  8. 8Create Jira IncidentJiraService
  9. 9Slack FinOps AlertSlackService
  10. 10Email Finance SummaryGmailService
  11. 11Log Run to SheetGoogle SheetsService

How it's built

Starts on
A clock
Steps
11, with 2 branches
Size
Medium: a working afternoon
Connects to
Gmail, Google Sheets, Jira, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Gmail, Google Sheets, Jira and Slack 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.