Control Bridge
ImpactControlBridgeWhen behavior is Stop and mode is active, the input value is passed directly to the output. When behavior is Mute/Bypass and mode is active, the node connected to the output is changed to active state. When behavior is Stop and mode is Stop/Mute/Bypass, the workflow execution of the current node is halted. When behavior is Mute/Bypass and mode is Stop/Mute/Bypass, the node connected to the output is changed to Mute/Bypass state.
Example
{
"class_type": "ImpactControlBridge",
"inputs": {
"value": [
"node_id",
0
],
"mode": true,
"behavior": "Stop"
}
}This example shows required inputs only. Connection values like ["node_id", 0] should reference actual node IDs from your workflow.
Inputs
| Name | Type | Status | Constraints | Default |
|---|---|---|---|---|
value | * | required | - | - |
mode | BOOLEAN | required | - | true |
behavior | ENUM3 options
| required | - | - |
Outputs
| Index | Name | Type | Is List | Connection Reference |
|---|---|---|---|---|
0 | value | * | No | ["{node_id}", 0] |
How to connect to these outputs
To connect another node's input to an output from this node, use the connection reference format:
["node_id", output_index]Where node_id is the ID of this ImpactControlBridge node in your workflow, and output_index is the index from the table above.
Example
If this node has ID "5" in your workflow:
value (*):["5", 0]