Building Scenarios

Saving a Scenario

After adding a scenario, rename it (if needed), add a description, and click Save.

---

Running a Scenario

One-time Execution

Click Run Once to execute the scenario once. This is useful for testing and debugging.

Depending on the trigger node:

• If the trigger node is an app node, create an event in the external application to trigger the scenario.
• If the trigger node is Trigger on Webhook, send an HTTP request to the node's URL.
• If the trigger node is Trigger on Schedule or Trigger on Run once, no additional actions are required.

After the scenario executes:

• Status icons (success / error) appear in the upper right corner of the nodes. Click on them to view details.

• A new entry appears in Execution History.

• The Data tab shows data from previous nodes.

• The Variables tab shows variable data (if variables were created).

You can stop a one-time execution by clicking Stop.

Automatic Execution and Activation

To enable automatic execution of the scenario, activate the scenario using the Active toggle at the bottom of the scenario page. When the scenario is active, it runs automatically in response to configured triggers (webhooks, schedules, or app events).

---

Deployment and Scenario Branches

Scenarios have two branches:

• Development: for testing configuration and data processing results
• Production: for the production version of the scenario

Development and Production can be edited and executed independently.

To create a new Development version and publish it to Production:

1. Click Save to create a new version.

2. Ensure that the next Development version appears in the version list.

3. Click Deploy.

4. Ensure that the Production branch appears in the version list.

If needed, you can roll back the Production branch:

1. Select a previous version.

2. Click Deploy to publish it to Production.

3. Check the Selected and Production labels on the published version.

---

Triggers and Scenario Branches

Each scenario has a trigger node that starts the scenario. The behavior of some triggers depends on whether the scenario is deployed and whether it is active.

Trigger on Webhook

The Trigger on Webhook node starts the scenario when an HTTP request is sent to one of the node's URLs (Production or Development).

• The Production branch is triggered by requests to the Production URL. Deploy the scenario and ensure it is active.

• The Development branch is triggered by requests to the Development URL. For requests to be accepted, either run the scenario once or activate it with the Active toggle.

Trigger on Schedule

The Trigger on Schedule node triggers the Production branch according to the configured schedule (while the scenario is active).

The Development branch is not triggered on schedule, but you can run it manually with Run once.

Trigger on Run once

The Trigger on Run once node triggers the Development branch when Run once is clicked. The Production branch is not triggered when Run once is clicked.

App Triggers

App trigger nodes behave differently depending on the branch:

• The Production branch is triggered at regular intervals (depending on your plan) if the triggering event in the app has occurred.

• The Development branch is not triggered by the app trigger node. After manual Run once, it will execute if the triggering event occurs in the app.

---

Other Settings

Aligning Nodes

At the bottom of the scenario page, use Align Nodes to horizontally align the scenario chain (when nodes are connected by links).

Stickers

Use Add Sticker to add notes to the scenario. Stickers are optional but can be used for comments, links, and code snippets.

You can resize a sticker by dragging its edges. Right-click on a sticker to:

• Copy — copy it to duplicate in the current or another scenario
• Delete — delete it