Message with buttons or a menu
Send buttons or a select menu, and continue the flow from whichever is used.
message.buttons sends a message with buttons, a select menu or both, then waits for someone to use one. Each button, and each choice of the menu, leads somewhere different.
Settings
| Setting | What it does |
|---|---|
| Message | The text to send. |
| Embed | One of your embeds. |
| Buttons and menus | A component set. Each button in it, and each choice of its menus, gets its own way out of this step. |
| Only visible to the user | Makes the message private. |
| Mentions that notify | See Mentions. |
Ways out
Sent, taken straight after the message is sent.- One way out for each button that has no action.
- One way out for each choice of a menu that has no action.
A button or menu with an action starts that action's flow instead, so it doesn't get a way out here.
Notes
Without an action they expire
A button or menu with no action continues the run that sent it, and only for a day. When the message should keep working, give it an action and handle it in a button action flow.
- The run is saved while it waits and takes no memory.
- Many people can be partway through the same step at once. Each press continues its own run.
- To wait for a typed answer or a reaction instead, use Wait for a reply.
Example
Send "Delete this channel?" with Confirm and Cancel buttons. Wire Confirm to Delete a channel and Cancel to Update the button's message.