Message buttons

Add a link button or a button that continues the automation to your message.

Add Buttons

Select the Message step on the workflow and scroll the side panel to the buttons. Select Add button to open its settings.

The editor shows the button layout you configured. Drag a button within a row to change its order, or into the gap between rows to create a new row. Platform limits may change the rows when the message is sent; button order and actions are preserved.

When the message has a branch button, the Allow buttons to be clicked multiple times setting appears. It is enabled by default, so each click can start the branch separately. When disabled, all branch buttons in this message become unavailable after the first accepted click; link buttons continue to work.

Select the required button to edit it. In the dialog, select the button type and appearance, then enter its text:

Branch transition continues the run through this button's separate output after it is selected. Save the button, then connect the new output beside the step to the next step;
Link requires an address that begins with https:// in the URL field. Selecting the button opens this address.

Appearance sets the semantic emphasis: Neutral, Primary, Positive, or Negative. A channel uses its closest supported style. In VK, the selected color applies to branch-transition buttons, while link buttons use VK's standard appearance. The website widget displays all four options with distinct styles.

The editor offers only button types supported by every channel selected for the step. Telegram, VK, MAX, Discord, and Widget support branch transitions and links. Email supports only a link and delivers it as a plain text URL. StreamVi and Avito do not support message buttons. If the set includes a channel without buttons, remove it only from this step's Channel types field; the automation can still start for that channel.

StreamVi is receive-only: you cannot send messages to it even without buttons. For a question with multiple selectable options and separate confirmation, use the Poll step.

Each button can contain up to 40 characters. Senler's overall limit is 40 buttons, but channels impose stricter layout limits:

Telegram: up to 8 buttons per row and 40 total;
VK: up to 5 per row, 6 rows, and 30 total;
MAX: up to 7 per row, but no more than 3 in a row containing a link; up to 30 rows and 40 buttons;
Discord: up to 5 per row, 5 rows, and 25 buttons;
Website widget: up to 3 per row, 5 rows, and 15 buttons;
Email: one link per row and up to 40 links.

For a step with several channel types, use the strictest limit among the selected platforms.

If a row is too wide, Senler moves some buttons to the next row. If there are still too many rows, it packs the buttons into fewer rows while preserving their order. For example, seven VK buttons configured one per row are sent in four rows: two buttons in each of the first three rows and one in the last.

If the buttons exceed the platform's total limit or still cannot fit into a valid layout, the automation message is not sent and the step fails. Extra buttons are not silently removed. Check the reason in the automation run.

To remove a button, open its settings and select Delete.

Send Buttons From An Agent Reply

If a Run agent step precedes the message, store its Response button block in a Run, Lead, Dialog, or Project variable. Then select Add button, choose Dynamic button block, select that result in the variable field, and select Add. For Lead and Dialog variables, check the selected message data source; in a background flow, they are available only in recipient-data mode.

The dynamic block appears among the regular button rows as a separate dashed card. Drag the entire card above, between, or below rows to choose where the agent's buttons appear in the message. Select the card to choose another variable, save the change, or remove the dynamic block. The agent's buttons and manually configured buttons are sent in one message in the selected order.

All dynamic branch buttons share one Button clicked output on the step. Connect it to the next step. Link buttons only open their URL and do not create a branch.

Under Save clicked button, choose a scope and an Object or JSON variable. When the lead selects a dynamic branch button, its identifier, text, and value are written to that variable. Run is suitable when the selection is immediately passed to Clicked button from variable in the next Run agent step. Lead and Dialog use the selected message data source, while Project stores a shared project value. In a Background automation, Lead and Dialog are available here only in recipient-data mode.

Dynamic buttons follow the same selected-channel limits and repeated-click setting as manually configured buttons. Limits and row wrapping apply to all buttons in the message together, not separately to the dynamic block.