Flow Toggle (2 Outputs)
AI-generatedOverview
This node manually routes workflow data to one of two outputs based on a user-selected toggle. It is useful for scenarios where you want to control the flow of data dynamically within a workflow, such as directing data to different processing branches or environments (e.g., production vs testing). For example, you can toggle data to output 1 for production processing or output 2 for testing without changing the workflow structure.
Use Case Examples
- Routing incoming data to output 1 for production processing.
- Routing incoming data to output 2 for testing or debugging purposes.
- Passing an empty signal to a selected output to trigger downstream nodes even when no input data is present.
Properties
| Name | Meaning |
|---|---|
| Route To | Determines which output (Output 1 or Output 2) the data will be sent to. |
| Options | Additional settings to control node behavior. |
Output
JSON
json_signal- An empty signal indicator when no input data is present and passEmptySignal is enabled._timestamp- Timestamp of when the empty signal was generated._flowToggle
*routedTo- Label of the output to which the data was routed, if routing info is added.
*output- Numeric index of the output to which the data was routed.
*timestamp- Timestamp when the routing info was added.
Troubleshooting
- If no input data is received and 'Pass Empty Signal' is not enabled, the node will output nothing. Enable this option to ensure downstream nodes receive a trigger signal.
- Ensure the 'Route To' parameter is correctly set to either 'output1' or 'output2' to avoid routing errors.
- If custom labels are used for outputs, verify they are set correctly to avoid confusion in routing metadata.