Automation library · Integrations

New Submission

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

Medium

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

The flow

Starts it 4Logic 8Service 2

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

  1. 1Webhook1WebhookStarts it
  2. 2Is List Request?IfLogic
  3. 3Get HistoryData TableService
  4. 4Is Save Request?IfLogic
  5. 5Sort By UpdatedSortLogic
  6. 6Prepare ContentCodeLogic
  7. 7Build PageCodeLogic
  8. 8Format History JSONCodeLogic
  9. 9Has Content?IfLogic
  10. 10Respond PageRespond To WebhookStarts it
  11. 11Respond HistoryRespond To WebhookStarts it
  12. 12Upsert EntryData TableService
  13. 13Format Save ResponseCodeLogic
  14. 14Respond SaveRespond To WebhookStarts it

How it's built

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

Questions

What does it need to run?

An n8n 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. 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.