Automation library · Alerts and monitoring

Recover abandoned event registrations

Started by a clock, and works across Email and n8n data table. 10 steps, 2 branches: a working afternoon to understand properly.

Medium

10 stepsMedium: a working afternoon
2Branches: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Logic 4Service 5

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

  1. 1Run Every 4 HoursSchedule triggerStarts it
  2. 2Query Incomplete RegistrationsHttp RequestService
  3. 3Calculate Recovery StageCodeLogic
  4. 4Has Carts to Recover?IfLogic
  5. 5Route by Recovery StageSwitchLogic
  6. 6Send Nudge Email (1h)Email SendService
  7. 7Send Social Proof Email (24h)Email SendService
  8. 8Send Last Chance Email (72h)Email SendService
  9. 9Log Recovery EventCodeLogic
  10. 10Log to Cart Recovery TableData TableService

How it's built

Starts on
A clock
Steps
10, with 2 branches
Size
Medium: a working afternoon
Connects to
Email, n8n data table
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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