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.

You can send text messages to StreamVi while the stream is live. Files and buttons are not supported.

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. 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 covers all automations in the project. The list is paginated; use the controls below it to move between result pages.

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

The status button shows Enabled or Disabled. Before the first publication, the automation is also disabled. A separate icon beside it shows “There are unpublished changes” or “All changes are published”. An automation can therefore be running while its draft contains changes that have not been applied yet.

To access actions for an automation, open the three-dot menu in its row.

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

In the menu, you can select Open, Usage chart, or open Runs in a separate dialog.

Read The List. Highlighted elements: 5. Open; 6. Runs — 5. Open · 6. Runs

Open the automation menu.

Creating And Listing Automations. 1. three-dot menu — 1. 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.

Creating And Listing Automations. Highlighted elements: 2. Copy; 3. Share — 2. Copy · 3. Share

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.

Creating And Listing Automations. 2. Run — 2 / 2
2. Run

Pause Execution

Open the status button and select Disable or Enable.

When you enable an automation from the list for the first time, Senler publishes the current draft and then enables execution. If a published version already exists, that version is enabled: new draft edits must be published separately in the editor.

Pausing temporarily stops new regular runs and the continuation of existing regular 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.

You can test the draft while the automation is disabled. Pausing the automation does not stop test runs; pausing the entire project or an individual test run still applies to them.

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 required automation's row.

Select Delete.

Creating And Listing Automations. 2. Delete — 2. 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.

Creating And Listing Automations. 3. confirmation dialog — 3. confirmation dialog

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.