Automation library · Integrations

Multi-channel event countdown manager with Slack and Email

Started by another system calling it, and works across Email. 11 steps, 2 branches: a working afternoon to understand properly.

Medium

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

The flow

Starts it 3Logic 6Service 2

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

  1. 1Schedule TriggerSchedule triggerStarts it
  2. 2Webhook TriggerWebhookStarts it
  3. 3Events DatabaseCodeLogic
  4. 4Process Webhook EventCodeLogic
  5. 5Is Slack?IfLogic
  6. 6Is Email?IfLogic
  7. 7Webhook ResponseRespond To WebhookStarts it
  8. 8Format Slack MessageCodeLogic
  9. 9Format EmailCodeLogic
  10. 10Send to SlackHttp RequestService
  11. 11Send EmailEmail SendService

How it's built

Starts on
Another system calling it
Steps
11, with 2 branches
Size
Medium: a working afternoon
Connects to
Email
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 another system calling it.

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. 11 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 11 steps before you point it at anything that matters.