Creating And Listing Automations

Create An Automation

On the Automations page, select Add. In the New automation dialog, first choose the automation type:

For dialogs when a run should start for the current dialog or lead;
Background when a run starts without an automatically assigned lead and dialog.

The selected type determines the available triggers, variable scopes, message recipients, and segment actions. You cannot change the type in the editor after creation.

In Channel types, select the platforms whose settings you plan to use in the steps. This selection helps the editor show compatible message and button options, but it does not restrict the channels that can trigger the automation. Telegram, VK, MAX, Discord, and Widget are selected by default; add StreamVi, Email, or Avito when needed. At least one channel type must remain selected.

Enter a name up to 160 characters long. A name is required. Select Create to open the new draft. Cancel closes the dialog without creating anything.

Create An Automation. Highlighted elements: 2. New automation dialog; 3. automation type; 4. Channel types; 5. name; 6. Create; 7. Cancel — 2 / 2
2. New automation dialog · 3. automation type · 4. Channel types · 5. name · 6. Create · 7. Cancel

Read The List

Use the search field above the list to filter automations by name. Search works on the project list that has already loaded.

An automation row shows its name, type, status, and last update time. Selecting the row opens the editor.

If no version has been published yet, Draft appears instead of a running state. After the first publication, the status button shows Running or Paused.

From the three-dot menu, you can select Open, Usage chart, or open Runs in a separate dialog.

Read The List. Highlighted elements: 1. search field above the list; 2. automation row; 3. status button; 4. three-dot menu — 1 / 2
1. search field above the list · 2. automation row · 3. status button · 4. three-dot menu

In the automation menu, select Copy to create a copy in the current or another project, or Share to transfer it by link.

Review the calculated package contents before starting. Linked segments and variable definitions are required when copying to another project. For a copy in the current project, you can leave them out and use existing resources. A link adds linked resources automatically. Trigger channels and message recipients from the source project may need to be selected again after import. See Resource copying for the complete workflow.

Start A Background Automation Manually

The background automation menu contains a Run action. It creates a working process from the published version and can pass initial variables to it. Contextual automations do not have this action in the list. For step-by-step instructions and the difference from testing a draft, see Start Step And Manual Run.

Pause Execution

Open the status button and select Pause or Resume.

Pausing temporarily stops new starts and the continuation of existing runs, but does not cancel them. A step that is already executing may still finish. After resuming, saved runs continue; a wait until a specified date is not reset.

In Runs, you can review the steps of a specific run, pause it temporarily, resume it, or cancel it permanently.

Delete An Automation

Open the three-dot menu in the row and select Delete. In the confirmation dialog, check the automation name. Delete removes the automation from the list and stops it from accepting new events; Cancel closes the dialog without changes.

You cannot restore a deleted automation through the interface. Deletion cancels its active runs and runs parked on a wait, interrupts pending agent replies, and removes unfinished timers. Steps that already completed and messages that were already sent are not rolled back. An automation from a ready-made solution cannot be deleted separately from its managing app.

Access

Viewing the list, opening the load chart, copying, and sharing by link require permission to view automations. Creating, deleting, pausing, resuming, and manual starts require permission to manage automations. Importing a copy requires manage access to every package resource type in the target project.