Automation library · Alerts and monitoring

Alert on API contract drift with Data Tables and Slack

Started by a clock, and works across Slack and n8n data table. 9 steps, 1 branch: a working afternoon to understand properly.

Medium

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

The flow

Starts it 1Logic 4Service 4

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

  1. 1Check on a scheduleSchedule triggerStarts it
  2. 2SettingsSetLogic
  3. 3Fetch the endpointHttp RequestService
  4. 4Load prior snapshotData TableService
  5. 5Skip run (no valid response)No OpLogic
  6. 6Derive schema and diff contractCodeLogic
  7. 7Update snapshotData TableService
  8. 8Breaking change found?IfLogic
  9. 9Post drift alert to SlackSlackService

How it's built

Starts on
A clock
Steps
9, with 1 branch
Size
Medium: a working afternoon
Connects to
Slack, n8n data table
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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