When to stop your automation campaign
A well-designed workflow knows when to stop. If a contact completes the action you were guiding them towards, makes a purchase, registers for the event, books the meeting, continuing to send the rest of the nurture sequence creates a poor experience. The emails are no longer relevant, and at best they're ignored. At worst, they generate unsubscribes or spam complaints.
The problem
Imagine a welcome series: Day 1 sends a welcome email, Day 2 suggests boards to follow, Day 3 prompts the contact to create their first board. If a new subscriber does all three things on Day 1, the Day 2 and Day 3 emails arrive after the contact has already completed every action you're asking for. The same pattern applies to any nurture sequence: a prospect who converts on the first touchpoint doesn't need seven more nurture emails. A customer who renews immediately after the first reminder doesn't need three follow-up reminders.
Technique 1: if/else check before each send block
Add an if/else block before each subsequent send in your sequence. The condition checks whether the contact has already converted, clicked the registration link, completed the form, or been added to a "converted" interest.
- If yes: route to an End block or to a more appropriate follow-up workflow.
- If no: continue to the next send block.

This is the most direct approach and works well when conversion can be detected via a single trigger, a link click, a form completion, or an interest assignment.
Technique 2: wait-until condition blocks
Instead of a fixed wait time between emails, use a wait block set to "wait until a condition is met". For example: wait until the contact clicks the registration link, or until 7 days pass, whichever comes first. If they click the link, they move immediately to the next block. If 7 days pass without clicking, they also move on.
Follow the wait block with an if/else that checks which condition was met, and route accordingly. Contacts who converted get an appropriate follow-up or exit. Contacts who didn't convert continue with the next nurture step.
Technique 3: a conversion interest
If conversion happens outside the workflow, through a direct purchase on your website, a CRM update, or any other external trigger, use a separate workflow to tag converted contacts. When a purchase is detected, a second workflow fires and adds the contact to a "Converted" or "Customer" interest.
In your nurture workflow, add an if/else block at each step that checks for this interest. Any contact who has been tagged as converted gets routed to an End block and stops receiving the nurture sequence.
Support tip Think of your workflow from the contact's perspective. At each step, ask: would this email still be relevant if the contact has already done what I'm asking? If the answer is no, add a condition that checks for it.
Pro tips
- Use internal notification actions to alert your sales team when a contact converts mid-workflow. This ensures the right follow-up happens even when the automation stops.
- Keep your "converted" interest or field consistent across workflows so different sequences all check the same signal and don't contradict each other.
- Review your workflows periodically to see whether contacts are exiting at the right points. If almost everyone is completing the full sequence, your conversion checks may not be firing correctly.
Common mistakes to avoid
- Using only fixed wait times between emails with no conversion checks. This is the most common cause of contacts receiving irrelevant emails after they've already taken the desired action.
- Building conversion detection for only the last email in the sequence. Add checks before each significant send, not just at the end.
- Removing an interest via a workflow that a contact assigned themselves. If a contact subscribed to something through their own preference, removing it automatically without their knowledge can damage trust. Apply conversion-based exits deliberately.
Next steps
- See "Create a workflow" for how to add if/else blocks and wait-until conditions to your workflow.
- See "Workflow examples" for concrete sequences that include conversion exit points.
- See "Workflow best practices" for broader guidance on designing workflows that stay relevant over time.