Workflow node reference
A/B Split
Randomly split traffic between paths. Exact configuration, outputs, execution behavior, errors, limits, and examples for the A/B Split workflow node.
What this guide covers
- Category: Logic.
- Use it to randomly distribute executions among named paths by percentage.
- 1 configuration fields and 2 documented outputs.
- Random allocation does not guarantee perfectly equal totals in small samples.
What this node does
Randomly split traffic between paths
Use it to randomly distribute executions among named paths by percentage.
When not to use it
Do not use it for rules based on customer data; use Condition or Classifier.
Prerequisites
- Valid JSON path definitions
- Unique path names
- Percentages that total exactly 100
- A connected branch for each path
Valid JSON path definitions. Unique path names. Percentages that total exactly 100. A connected branch for each path
Inputs and configuration fields
| Field | Key | Control / type | Requirement | Default | Accepted values and behavior |
|---|---|---|---|---|---|
Paths | paths | json | Required when shown | No default | Define paths and their percentages (must total 100%). [{ "name": "Path A", "percentage": 50 }, { "name": "Path B", "percentage": 50 }] |
Configure the node
- Drag A/B Split from Logic in the node palette.
- Select the node to open its configuration drawer.
- Complete every required field and any conditional field revealed by your choices.
- Insert variables only from the current trigger or an earlier node on the same path.
- Connect every required output handle to the intended next step.
- Save and run Workflow Test with representative data before activation.
Outputs
Later nodes can use these values only after this node has run successfully on the same execution path.
| Variable | Type | Meaning |
|---|---|---|
{{nodes.split.selected_path}} | string | Name of chosen path |
{{nodes.split.path_index}} | number | Index of chosen path |
Execution behavior
- Randomly selects one configured path.
- Emits selected path and path index.
- Each execution follows only the chosen path.
Do not assume a failed node is automatically retried. Review the execution result and the relevant service documentation before repeating an operation that could create a duplicate side effect.
Example use case
Send Variant A to 50% of eligible inbound leads and Variant B to 50%.
Keyword Match → A/B Split → Send Text A / Send Text B → End FlowCommon errors
| Symptom | Resolution |
|---|---|
Configuration is invalid | Make every percentage numeric and ensure the total is 100. |
A path stops | Connect the generated handle for that path. |
Limitations
Random allocation does not guarantee perfectly equal totals in small samples.
No built-in statistical significance report is exposed.
Random allocation does not guarantee perfectly equal totals in small samples. No built-in statistical significance report is exposed.