Automation library · Alerts and monitoring

Sync nightly TeamRetro health check scores with Postgres

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

Medium

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

The flow

Starts it 1Logic 6Service 6

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

  1. 1Nightly at 02:00Schedule triggerStarts it
  2. 2Ensure Table ExistsPostgresService
  3. 3Get TeamsTeam RetroService
  4. 4Latest Health CheckTeam RetroService
  5. 5Has a Closed Check?IfLogic
  6. 6Get DimensionsTeam RetroService
  7. 7Collect OutcomesMergeLogic
  8. 8Normalise RowsCodeLogic
  9. 9Run SummaryCodeLogic
  10. 10Valid Row?IfLogic
  11. 11Any Errors?IfLogic
  12. 12Upsert ScoresPostgresService
  13. 13Alert on FailuresSlackService

How it's built

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

Questions

What does it need to run?

An n8n account, plus your own Postgres 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. 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.