Automation library · Integrations

Distribute workflow execution

Started by an event in a connected app, and works across n8n data table. 9 steps, 1 branch: a working afternoon to understand properly.

Medium

Download free
9 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Logic 6Service 2

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

  1. 1When clicking ‘Execute workflow’Manual triggerStarts it
  2. 2Calculate the next route to useData TableService
  3. 3Merge trigger data to pass to subworkflow if neededMergeLogic
  4. 4Code in JavaScriptCodeLogic
  5. 5Round Robin RouterSwitchLogic
  6. 6Update last_used in the datatableData TableService
  7. 7Route 1No OpLogic
  8. 8Route 2No OpLogic
  9. 9Route 3No OpLogic

How it's built

Starts on
An event in a connected app
Steps
9, with 1 branch
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 an event in a connected app.

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