Skip to main content
A button can change its originating message after a click. Open the button’s action settings, enable Message Update, choose a strategy, and configure the replacement/response blocks.

​
Choose the scope of the update

Available strategies depend on whether the button is in an Actions block, section accessory, Context Actions, card, or carousel. See the position matrix before configuring API-authored actions.

​
Configure an approval result

  1. Enable idempotency for the action; it is required for message updates.
  2. Choose replace_actions_block for an approval button in an Actions block.
  3. Add a Context response saying Approved by {{user.name}}.
  4. Save and send a new test message.
  5. Click the action, verify which blocks changed, then inspect its interaction outcome.
Original data is under context.*; the click actor is under user.*. See payload variables. For a targeted replacement, retain stable block IDs and specify the actual target_block_id. A nonexistent block, deleted Slack message, or invalid replacement can make the update fail.

​
Combined effects and repeated clicks

A webhook and message update are separate effects. Check each component in history rather than inferring that both succeeded. Use an idempotency policy appropriate to the business action and deduplicate at your receiver. For modal submissions, close_behavior determines when an update runs after the webhook outcome; see Submissions. Changes to the template do not update the configuration stored in old messages. Send a new test message after editing actions. Button webhooks · Interaction history