Switch Node
Routes workflow execution to different branches based on conditions defined on workflow variables.Evaluation Behavior
- Conditions are evaluated top-to-bottom by branch order
- If multiple branches match, the workflow takes the first matching branch
- If no branches match, the workflow takes the Default route
Configuration Guidance
Timestamp Comparisons
When comparing timestamps in Switch conditions, use the format:HTTPS Node
Performs HTTP requests (GET/POST/DELETE/etc.) to external APIs or custom endpoints, and maps response fields to workflow variables.Request Configuration
Output Variables (Response Mapping)
Maps response fields into workflow variables so they can be used in downstream nodes.Retry Behavior
Wait Node
Pauses workflow execution for a specified duration or until a target time.Modes
Timer (Relative)
Timer (Relative)
Waits for a relative duration from the current time.Example: Wait 5 minutes.
Scheduled Period (Absolute)
Scheduled Period (Absolute)
Waits until a specific timestamp is reached.Example: Wait until a specific date and time.Scheduled Period supports a Regular Expression field where a Jinja expression can produce the target timestamp.
Variable References in Jinja
- Workflow variables can be referenced directly by name (e.g.,
disposition_ptpdatetime) - System variables are referenced as
system_variables.<name>(e.g.,system_variables.current_datetime)
Example Jinja Expression
Telephony Node
Places an outbound voice call using a configured agent. The telephony node uses Instant Outbound internally.If a non-Exotel phone number or provider is required, ensure that provider is supported for Instant Outbound.
Agent Configuration
Connection and Phone
Specifies the telephony connection and the phone number to use. Because Instant Outbound is used internally, it is not required to link a phone number to the agent in the Deploy section, provided:- The connection exists
- The phone number is valid for that connection
Output Variables (Output Mapping)
Maps agent variables → workflow variables after the call completes. Use this when downstream workflow logic needs updated agent outputs (e.g., disposition, collected identifiers, status).Agent variables are often strings. Keep workflow variable types aligned, or ensure comparisons/operators match the resulting types.