Automation library · Alerts and monitoring

Real-time flight tracking with Aviation API and Slack

Started by a clock, and works across Postgres. 13 steps, 2 branches: a working afternoon to understand properly.

Medium

Download free
13 stepsMedium: a working afternoon
2Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Logic 3Service 9

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

  1. 1Schedule TriggerSchedule triggerStarts it
  2. 2Fetch Airline DataHttp RequestService
  3. 3Get Current SchedulesPostgresService
  4. 4Process ChangesCodeLogic
  5. 5Check for ChangesIfLogic
  6. 6Update DatabasePostgresService
  7. 7Check Urgent NotificationsIfLogic
  8. 8Notify Slack ChannelHttp RequestService
  9. 9Get Affected PassengersPostgresService
  10. 10Update Internal SystemsHttp RequestService
  11. 11Send Email NotificationsHttp RequestService
  12. 12Log Sync ActivityPostgresService
  13. 13Send SMS (Critical Only)Http RequestService

How it's built

Starts on
A clock
Steps
13, with 2 branches
Size
Medium: a working afternoon
Connects to
Postgres
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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