​

Buttons

Buttons is the flexible action building block. Each button can run a sequence, e.g. update a property, create a task, reload data, and show a confirmation.

​

Availability

Buttons can be used in every placement. They must not be placed inside a Repeater, because the block id would otherwise be repeated for every row.

​

Add and configure

A new block starts with one primary button. For each button you can set:

• Button label — fixed or dynamic text;
• Appearance — primary, secondary, or critical;
• When the button is clicked — a list of actions.

Choose Add button to go up to three buttons. Each button must have at least one and at most 10 actions.

​

Actions

Buttons support CRM updates, tasks, connector calls, toasts, links, data reloads, form values, conditional branches, and — on flow cards — navigation and submit. The actions run in order and stop at the first error. Open a link must come last. See Actions for all types and fields.

​

Data, rules, and steps

Button labels and action values can use dynamic data. The whole button row can be assigned to a step and have a visibility rule. On flows, you can either use the automatic navigation buttons or build your own with Buttons. Avoid two competing navigation sets on the same step.

​

Limitations and tips

The current inspector can add buttons but has no separate control for removing or reordering the buttons themselves. Action rows, on the other hand, can be moved and removed. If the button setup is wrong, it may be fastest to recreate the whole building block. Use only one primary action in a visible area. Use the critical appearance for actions with a real negative consequence, and consider showing an explanation or confirmation.