Guide

Build

Branching, merging & loops

1 min readOpen in Neblex

There are no special "if" or "switch" nodes: you branch with conditions on edges.

  • If / else: draw two edges out of a node. On one, turn on Only pass matching records with a condition (for example amount greater than 1000); on the other use the opposite (amount less than 1001).
  • Switch: draw one edge per case, each with its own condition, such as region equals EU, US, APAC.
  • Merge: connect several edges into one node; it receives the records of all incoming edges, in edge order. Follow with Merge by key if you need to combine fields.
  • Parallel: steps that do not depend on each other can run at the same time; the platform schedules them.
  • Skipped branches: a branch that receives no records does not run its adapter, Wait, Wait for event, Wait for form or Code steps. They show as skipped in the run.
  • Branch on errors: set a step's On error to Route the error onward and branch on error exists / does not exist. See Error handling.
  • Branch on decisions: after Wait for form, branch on _outcome. After Remove duplicates with branching, use the Unique and Duplicate outputs.
  • Branch on changes: after a CDC poll, branch on _change equals insert, update or delete.

Repeating steps

  • Loop node: the recommended way to repeat a group of steps. See the Loop card.
  • Loop back edge: on an edge that points back to an earlier node, turn on loop back and set Maximum repeats (default 3, up to 10,000). The section between them repeats while the edge's condition holds (or up to the maximum when there is no condition). Loop-back edges carry no data; keep state with Set value.
  • Repeat for each record in a step's advanced settings runs that single step once per record, optionally in parallel. See below.