Editing a published automation, and duplicating one
Live edits apply immediately — here's exactly what that means for in-progress conversations.
Details
Open any automation from the Automations list to edit it, published or not. Changes to a published automation take effect immediately on save — there’s no separate “republish” step and no staging/preview version running alongside the live one.
What happens to a conversation already in progress
A contact partway through a multi-step flow when you edit it continues from where they currently are in the updated graph, not from the beginning — if you change a message earlier in the flow, someone already past that point won’t see the new wording, but someone who hasn’t reached it yet will. If you need to guarantee every future conversation starts fresh from a clean version, duplicate the automation instead of editing the live one, pause the original once the duplicate is live, and let existing in-progress conversations finish on the original.
Duplicating
Click the duplicate icon next to any automation to create an exact copy as a new draft, with “(copy)” appended to its name — useful for a seasonal variant, an A/B test of different wording, or the “guarantee a clean start” pattern above. A duplicate starts in draft status regardless of the original’s status, so it never accidentally goes live before you’re ready.
More in Automations & the flow builder
Trigger types: comments, DMs, and story mentions
What each one watches for, keyword matching rules, and priority order.
The flow builder: nodes, branching, and delays
Skip it for a single message, or design a full multi-step conversation.
Sending automation data to Google Sheets or Zapier
The webhook node: what it sends, security limits, and what happens if it fails.
Testing an automation before it goes live
Preview the full conversation without sending anything real.
Didn’t answer it? Email [email protected].