Robots are automated actions triggered at pipeline stages. When a deal enters a stage, a robot automatically performs the action you configured: sends a message to the customer, creates a task for a manager, changes a tag, moves the deal to another stage, or launches a bot scenario.

Robots are configured separately for each stage. You can add multiple robots to the same stage: they can run immediately, after a specified delay, or sequentially one after another.

How to Open Robots

Step 1. Open the “CRM” section and select the pipeline you need.

Step 2. Click “Robots” in the top panel, next to the pipeline filter and settings.

The Robots page for this pipeline will open. Each stage is displayed as a separate column, with its robots listed below the stage name.

In the top panel:

  • “Back to Board” — return to the deals in this pipeline;
  • pipeline selector — open the robots for another pipeline;
  • “Cancel” and “Save” — discard or save all changes made on the page.

If there are many stages, you can scroll the board horizontally using the arrow to the right of the stages or by clicking and dragging an empty area of the board. The list of robots in each column scrolls separately.

Important! Robots can only be added to pipeline stages. You cannot add robots to “Unsorted,” “Won,” “Lost,” or the archive.

How to Add a Robot

Step 1. Click “Add Robot” below the robot cards in the required stage.

Step 2. Select an action. Actions are divided into groups: “Customer,” “Employees,” “Deal,” “Tags and Lists,” “Bot and Scenarios,” and “Integrations.” To quickly find the action you need, use the search field at the top of the window. You can also change the stage where the robot will be added directly in this window.

Good to know! If the action you need is not on the list, use the “Launch Scenario” robot. It can send the customer to any branch of your bot, where you can configure any required actions.

Step 3. The robot settings panel will open on the right. Configure the action parameters and, if necessary, change when the robot runs, its conditions, and protection settings. Each section is described in more detail below under “Robot Settings.”

Step 4. Click “Done” to close the panel.

Step 5. Click “Save” in the top panel of the page.

Important! All changes on the page — new robots, edits, deletions, and rearrangements — take effect only after you click “Save.” The number next to the button shows how many changes have not yet been saved. If you close or reload the page without saving, your changes will be lost. A warning will appear before you leave the page.

The “Cancel” button in the top panel restores all robots in the pipeline to their last saved state. The “Cancel” button at the bottom of the robot settings panel discards only the changes made to that robot since you opened the panel. If the robot has just been added, this button removes it.

By default, a new robot:

  • is enabled;
  • runs immediately when a deal enters the stage;
  • does not wait for other robots;
  • runs without conditions;
  • is canceled if the deal leaves the stage;
  • does not message the customer while an operator is communicating with them.

Until all required fields are completed, the robot card is orange and displays “Not configured — open to fix.” You can save such a robot, but it will not run. After saving, a notification will show how many robots are not configured.

Robot Settings

To open the settings, click the robot card or select “Configure” from the “⋯” menu on the card.

The panel header shows the robot name, stage, and its position in the column, for example, “robot 2 of 5.” You can rename the robot by clicking the pencil icon: for example, “Payment Reminder” instead of “Send Message.” If you delete the custom name, the default name will be restored.

The panel contains the following sections:

  1. “When to run.”
  2. “Queue.”
  3. “Condition.”
  4. Action parameters. The section title depends on the action: “Message,” “Task,” “Stage,” and so on. The parameters for each action are described in the “Types of Robots” section. For robots without configurable parameters — “Unsubscribe from Mailings,” “Cancel Scheduled Messages,” and “Mark Conversation as Unread” — this section contains only a description of the action.
  5. “Protection.”

Changes are immediately reflected on the robot card on the left. You can close the panel by clicking “Done,” the close icon, pressing Esc, or clicking outside the panel. The changes will remain on the page, but you must click “Save” for them to take effect.

When to Run

This setting determines when the robot performs its action:

  • “Immediately when the deal enters the stage” — the robot runs a few seconds after the deal enters the stage.
  • “After” — runs after the specified number of minutes, hours, or days. For example, “After 1 day” means exactly 24 hours after the deal enters the stage.
  • “At a specific time” — runs at the specified time according to the project's time zone. There are two options:
    • “today or tomorrow” — if the deal enters the stage before the specified time, the robot runs today; if it enters later, the robot runs tomorrow;
    • “the next day” — the robot always runs at the specified time on the following day.
  • “… before” — runs a specified amount of time before a date stored in a deal field. For example, 1 hour before a scheduled consultation.

How the “… before” option works:

  • the list contains deal fields displayed on deal cards. These are selected in the pipeline settings under “Display variables on deal cards.” If the list is empty, add the required field there;
  • the deal field must contain a date and time, for example, 25.10.2026 14:00. A date without a time, such as 25.10.2026, is treated as midnight on that date;
  • if the field is empty or does not contain a valid date, the robot will not run. The log will show “Canceled: the deal field does not contain a date”;
  • if the required time has already passed, the robot runs immediately. For example, if a customer books a consultation 30 minutes before it starts while the robot is configured to run 1 hour before;
  • the date is taken from the deal when the deal enters the stage. For a robot with the “After previous” queue setting, the date is taken when the previous robot finishes. If the date in the deal is changed afterward, the scheduled run time will not change.

The robot card displays the run time in a shortened format: “Immediately,” “After 2 hours,” “At 10:00,” or “1 hour before ‘Consultation date’.”

Important! The run time is calculated when the deal enters the stage. For a robot with the “After previous” queue setting, it is calculated when the previous robot finishes. If you later change “When to run” or “Queue” and save the changes, already scheduled runs will still use the old timing. Other settings — text, conditions, parameters, and whether the robot is enabled — are retrieved when the robot actually runs, so changes to these settings also apply to already scheduled runs.

Queue

  • “Independent” — the robot does not wait for other robots in the stage. The time specified under “When to run” is counted from the moment the deal enters the stage.
  • “After previous” — the robot waits until the robot above it in the column finishes, and only then starts counting its own delay. For example, “After previous · after 1 hour” means one hour after the previous robot finishes.

You can change the order of robots in a column by dragging their cards. The queue runs from top to bottom.

Example. There are three robots in the “Invoice Sent” stage:

  1. “Send Message” with the invoice — “Immediately.”
  2. “Send Message” with a reminder — “After previous,” after 1 day.
  3. “Create Task” for the manager to call the customer — “After previous,” after 2 hours.

The customer receives the invoice, then a reminder one day later, and two hours after that the manager receives a task. If the customer pays earlier and the deal leaves the stage, the remaining robots will not run, provided that the “Cancel if the deal leaves the stage” protection setting is enabled.

Good to know! “After previous” waits for the previous robot to finish regardless of its result, not only when it succeeds. If the previous robot ends with an error, is skipped, or its condition is not met, the next robot will still run. The robot waits for the nearest robot above it that is scheduled to run when the deal enters the stage. Disabled and unconfigured robots, as well as robots that have already run for this deal and are not configured to run again, are skipped. If there is no eligible robot above it — for example, if all robots above are disabled — the robot works as “Independent.”

Condition

Without conditions, the robot runs for every deal at the stage. To make the robot run only for specific deals, click “Add Condition” and select a field, comparison operator, and value.

Field Comparison What is checked
“Deal amount” >, <, =, ≠ The deal amount. You can enter “15 000” or “15000,50”. If no amount is specified, it is treated as zero
“Customer tags” “contains”, “does not contain” Whether the customer has the selected tag
“Customer lists” “contains”, “does not contain” Whether the customer belongs to the selected list
“Assignee” “is”, “is not” The deal assignee. If there is no assignee, “is” is not satisfied, while “is not” is satisfied
“Customer channel” “is”, “is not” The bot through which the customer communicates, for example, “Telegram: @shop_bot”
Deal field “…” “equals”, “does not equal”, “empty”, “filled” The value of the deal field. The comparison is exact; leading and trailing spaces are ignored