🇪🇸 Español 🇬🇧 English 🇧🇷 Português

Node: Parallel

How to use the Parallel node to run several branches of a workflow from a single point.

Jul 11, 2026

The Parallel node is a fan-out node: from a single point in the flow, it opens several output branches (b1, b2, ... bN) representing independent paths of the workflow. It's the way to say "from here, do all of these things" instead of chaining actions one after another.

When to use it

  • When a single event needs to trigger several actions that don't depend on each other — e.g. notify the team via Team AND message the contact AND create a task, all off the same trigger.
  • As a starting point before a Merge node, when the flow needs to wait for every branch to finish before continuing.

Requirements

  • None special: any trigger can feed into a Parallel node.
  • Each declared branch needs at least one node connected to its output handle (b1, b2, etc.); a branch with nothing connected simply does nothing.

Configuration

  • Branch count (branches, required): an integer between 1 and 5 (default 2). Sets how many output handles (b1...bN) appear on the canvas.

Example

A workflow fires when a contact is flagged as VIP. The Parallel node with 3 branches connects: b1 → Publish to Team (alert the sales team), b2 → Send a welcome message to the contact, b3 → Create a follow-up task on the CRM board. All three actions run off the same trigger, independently of each other.

Tips

  • In this version, branches run sequentially (b1, then b2, ... bN) within the same run, not truly in parallel at the infrastructure level — but each branch's logic is independent.
  • Changing the branch count doesn't delete existing edges: if you lower it from 5 to 2, the b3/b4/b5 connections stay saved (just inactive) in case you raise the count again later.
  • Close the fan-out with a Merge node if the rest of the flow needs to wait for every branch to finish before proceeding.

Troubleshooting

  • One branch does nothing: check that its output handle (b1, b2...) has a node connected — with nothing connected, that branch simply doesn't execute anything.
  • The flow hangs after a Merge: if a branch never reaches the Merge (e.g. cut off by a condition), the Merge waits indefinitely. Add a wait_until_event with a timeout if a branch might not run.
Was this helpful?

Related articles