Skip to main content
Use the Studio flow editor to send different saved messages based on the buttons a recipient chooses. Switch to a Studio workspace with permission to create or edit automations.

​
Build and save

  1. Open the flow editor and create an automation, or open an existing automation and explicitly convert its DM node into a message flow. Opening an ordinary automation alone does not convert it.
  2. Configure the trigger and the first message. Add optional opening, follow, or email steps.
  3. Add a button to open an HTTP(S) link or send another message. For a message button, create a destination or select an existing message.
  4. Connect all messages to the entry. You can reuse a destination across branches or create a return button to an earlier message.
  5. Preview, save, and activate. Test each branch from another account.
A flow supports up to 50 messages, each with up to three buttons and button labels of 1–20 characters. Messages allow 1–640 characters; photo cards need a 1–80 character title. Instagram text without buttons also has a 1,000 UTF-8-byte limit. A link button opens the destination and records a click; it does not send the next message. A message button requires a recipient tap for each transition. Loops do not run automatically, and flows are not scheduled drip campaigns. Each successfully sent follow-up uses the workspace sending allowance.

​
Edit an active flow

Save changes to apply them to new runs. Buttons already delivered continue to use the original flow snapshot. Pause or delete the automation to stop future sends, including continuations. Messaging windows, channel access, and billing limits still apply.

​
Show performance on the canvas

For a saved flow, enable Show performance in the gear menu. Choose 7, 30, or 90 days. You need analytics access as well as automation viewing access. Save message changes before viewing metrics; refresh manually or wait for the minute refresh. The period selects runs that started then and includes their later activity. Entry counts start at the message flow, after preceding gates, rather than at the trigger. Cards show people reached and delivery outcomes; repeated visits can put a person in more than one outcome. Buttons show distinct clickers and a rate based on people sent that button and destination. One person may click several branches, so rates are not mutually exclusive shares. Trigger, public-reply, and gate steps without tracking are marked unavailable. Older button data may be incomplete.