Skip to content
ExplainerSlackMS TeamsDiscordGoogle ChatAdminMember

Interactive messages and buttons

Interactive messages and buttons

Dailybot can send messages with buttons so a person can take the next action without leaving the conversation. Buttons work across Dailybot’s supported chat platforms, while the outcome behind a button depends on how the message was configured.

A link button opens a secure web URL. Use it when the destination already owns the task, such as a run log, document, issue, or dashboard.

An interactive button sends a structured action through Dailybot. Depending on the supported configuration, it can:

  • send an action to an external callback;
  • open or submit a Dailybot form;
  • trigger a saved Dailybot workflow;
  • run a supported command or prompt;
  • open a modal to collect more information;
  • show a response to the person who clicked.

Use the Messaging API reference to confirm which options can be combined and which fields are required. That reference is the source of truth for the button contract.

Choose the smallest useful outcome

Start with what should happen after the click. If the user only needs to open another system, use a link. If Dailybot already owns the form or workflow, point the button to that resource. Use an external callback when your application must receive and process the event.

Keep the label specific to the action. A person should know whether a button opens a page, approves a request, starts a workflow, or asks for more information before clicking it.

Secure external callbacks

Treat button callbacks as authenticated events, not as trusted browser input. Use HTTPS, verify the callback signature according to the Messaging API security guidance, and process repeated delivery safely. Do not place secrets in button values, labels, message text, or callback URLs.

Your callback should return a clear success or error outcome. Log the event identifier needed for diagnosis without logging credentials or sensitive response content.

Test the complete flow

Send a test message to a private destination before using it with a team. Click every button, cancel and submit any modal, confirm the expected form or workflow runs, and verify what the user sees after the action.

For visual examples, see trigger workflows from chat and add approval gates to CI/CD. For exact API and CLI examples, use the maintained Messaging reference.