Automation library · Alerts and monitoring

Monitor Klaviyo list decay with Postgres and Gmail

Started by a clock, and works across Gmail and Postgres. 16 steps, 1 branch: a working afternoon to understand properly.

Medium

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

The flow

Starts it 2Logic 8Service 6

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

  1. 1Schedule: Daily 2AMSchedule triggerStarts it
  2. 2Error TriggerError triggerStarts it
  3. 3Set: Initialize RunSetLogic
  4. 4Prepare Error DataCodeLogic
  5. 5Get All ProfilesHttp RequestService
  6. 6Log Error to DBPostgresService
  7. 7Extract Profile ItemsCodeLogic
  8. 8Send Error AlertGmailService
  9. 9Score ProfilesCodeLogic
  10. 10Log Profiles to DBPostgresService
  11. 11Build Run SummaryCodeLogic
  12. 12Is Critical?IfLogic
  13. 13Insert Run SummaryPostgresService
  14. 14Suppress Critical in BatchesCodeLogic
  15. 15Build Email HTMLCodeLogic
  16. 16Send a messageGmailService

How it's built

Starts on
A clock
Steps
16, with 1 branch
Size
Medium: a working afternoon
Connects to
Gmail, Postgres
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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