Each button and list option can carry your own payload
In Auto Flows, every option in a Send buttons or Send list step can now carry a payload you choose — sent back when it is tapped, saved as the answer and passed to your Webhook step.
Released 23 September 2026
Know exactly which option a customer tapped, in your own words: give every button and list option a payload of your choosing.
What's new
- A payload for every option. In Send buttons and Send list steps, each option has a new Payload box. Whatever you put there — an order code, a product code, a campaign tag — is what comes back when the customer taps it. Leave it blank and the option's own key is used.
- Saved as the answer. Save to now stores the payload (or the key, when there is none), so your variables, contact fields and tags carry the value you chose. Rules you wrote against the key keep working.
- Your systems get the tap. The Webhook step now sends a
replywith the payload, the text the customer saw, and the option and step it answered. - Taps land in the right flow. When a customer taps an option, only the step that sent that message moves on. Another flow waiting on its own buttons or list keeps waiting, instead of taking its "no match" path.
- Your wiring stays put. Adding or changing a payload never disconnects a branch.
- A heads-up on opt-out words. A payload such as "unsubscribe" opts the contact out when it is tapped, so the builder points it out before you publish.