How to use an action in a Scenario Builder scenario?

Scenario Builder is a new module that replaces Scenario Dialog. Actions extend scenario functionality: integrate with external systems, process data, execute complex logic.

When you need it

• You need to integrate the scenario with CRM, API, or other systems.
• You need to perform calculations, validate data, or make external requests.
• You need to send email, create a ticket, or call an external service.

What you need to know

• Action — an action from the actions library (ActionJail) that can be used in a scenario.
• Form mode — in Scenario Builder, actions are configured through a UI form instead of raw JSON. You can switch to JSON mode for manual editing when needed.
• Documentation in panel — for each action type, Node Inspector shows built-in documentation and hints for parameters.
• Test action — in the node config panel you can test the action with the current state.

Before you start

• You are logged in with integrator or administrator rights.
• You have an open scenario in Scenario Builder.
• The required action is created in the actions library (ActionJail).

Step-by-step instructions

1. Add Action node

1. On the canvas, click «+».
2. In the modal, select category Data or Main.
3. Select node type Action.
4. The node appears on the canvas.

2. Connect to previous node

1. Drag an edge from the previous node (e.g., WaitForInput) to the Action node.
2. Connect the Action to the next node according to the scenario logic.

3. Configure the action

1. Click on the Action node — Node Inspector opens on the right.
2. Select the action template from the actions library.
3. Fill in parameters through the form (fields, dropdowns, rules). Built-in documentation and hints are shown for each action type.
4. Use process variables in the format {{variable_name}}.
5. If needed, switch to JSON mode — for manual configuration editing (when the action supports this mode).

4. Test the action (optional)

1. In Node Inspector, find the «Test action» or «Test» button.
2. You can pull state from the last run («From last run»).
3. Run the test — the result displays in the panel.

5. Save changes

1. Click «Save» in the toolbar.

Related materials

• Scenario Builder hub
• Built-in actions reference — common routing, operator, Custom Data, schedule, and timer actions
• Actions library (ActionJail)
• Actions reference
• Scenario Dialog — actions in scenarios — action concepts (apply to Scenario Builder too)