How do I build a list of buttons with Workflows

This article explains how to show users a list of buttons and branch your workflow based on their choice.

Button pickers are one of the easiest ways to guide users through a structured flow. They help users choose a department, topic, product, or next step without typing, and they make your workflow easier to test because each choice can lead to a predictable branch.

Creating our list of Button Pickers

Inside of your workflow, you can open the Block Drawer from the left to drag a new Action block "Send Message: Button Picker" and start configuring the buttons you'll want to implement in your flow.

You will then need to add an Event block "Button/Field Action" for each of the button you created in the previous step. Each of this Event block should be added as a new child in order to split the workflow into multiple branches, to have individual flows for each of our buttons.

While you can drag/add individual Event blocks for each button, you also have a shortcut allowing you to quickly do so for buttons! Simply hover each of the buttons of your Action block to display a lightning icon enabling you to add a pre-configured Event block for each of your buttons.

Let's see an example right away to illustrate the setup!

Let's now review the details of the configuration:

This allows you to add more translations to your buttons, which will be displayed accordingly based on their language preferences. The "default locale" will be the default one if the user's language doesn't match one of the additional locale you configured.
The message attached to your picker message
This is where you can add/remove buttons and set their label (the text appearing on the button).

You can add more buttons and delete some if you wish. The "blue gear" icon will allow you to configure some additional properties, if you would like you to change the button's identifier (used to link a button's action block to the corresponding event block), or if you want your button to open a link when clicked instead.

This option can be toggled to turn a button mandatory. This means that the user will not be able to send message until a button has been clicked.
The type of "action" we want to detect. In our case, this is a "Button Click".
The Match value determines which of the previously created button this block should be detecting. You will be able to select a button from the ones you previously created, or input a different "identifier" if you have set a customized one during on step 3.
Allows you to memorize the value of that button inside of a key, which you can later use as a variable inside of a message, or to update a user's information.

And voilà ! Your list of button choices is now ready! You can try these directly from the "Test" area of the Workflow Editor. 💬

Updated on: 04/05/2026

Was this article helpful?

Thank you!