Automation library · Alerts and monitoring

Send nightly staging vs production drift digest

Started by a clock, and works across Google Sheets and Slack. 12 steps, 2 branches, 1 loop or waits: a working afternoon to understand properly.

Medium

12 stepsMedium: a working afternoon
2Branches: places the flow splits
1Loop or waits
2Services it connects to

The flow

Starts it 1Logic 7Service 4

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

  1. 1When Every Night at 2AMSchedule triggerStarts it
  2. 2Read Staging Path ListGoogle SheetsService
  3. 3Loop Over PathsSplit In BatchesLogic
  4. 4Build Staging Drift DigestCodeLogic
  5. 5Build Environment URL PairCodeLogic
  6. 6Check for Significant DriftIfLogic
  7. 7Compare Staging to ProductionSnapshot SiteService
  8. 8Notify Staging Drift on SlackSlackService
  9. 9Notify Quiet Night on SlackSlackService
  10. 10Check for API ErrorIfLogic
  11. 11Record Failed PathSetLogic
  12. 12Record Drift ResultCodeLogic

How it's built

Starts on
A clock
Steps
12, with 2 branches, 1 loop or waits
Size
Medium: a working afternoon
Connects to
Google Sheets, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Google Sheets 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. 12 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 12 steps before you point it at anything that matters.