Automation library · Alerts and monitoring

Merged API results WIP with Discord and Notion

Started by another system calling it, and works across Discord and Notion. 14 steps, 3 branches: a working afternoon to understand properly.

Medium

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

The flow

Starts it 1Logic 10Service 3

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

  1. 1WebhookWebhookStarts it
  2. 2TEST RequestHttp RequestService
  3. 3IF address OKIfLogic
  4. 4IF1IfLogic
  5. 5Invalid AddressSetLogic
  6. 6IF2IfLogic
  7. 7Invalid EmailSetLogic
  8. 8Set All OKSetLogic
  9. 9Invalid SigSetLogic
  10. 10DiscordDiscordService
  11. 11NotionNotionService
  12. 12Set ResponseSetLogic
  13. 13Set Response1SetLogic
  14. 14MergeMergeLogic

How it's built

Starts on
Another system calling it
Steps
14, with 3 branches
Size
Medium: a working afternoon
Connects to
Discord, Notion
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Discord and Notion accounts. 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. 14 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 14 steps before you point it at anything that matters.