Automations
Conditions, branches and timing
Use If/Else, wait steps and A/B tests in an automation, and chain several automations with tags without creating a loop.
If you haven’t built an automation before, start with Get started with automations.
If / Else
The If / Else step splits the flow into a Yes branch and a No branch. Whoever meets the condition takes the yes path, everyone else the no path.
A condition is a field, a comparison and a value:
| Field | Comparisons |
|---|---|
| Tags | Contains · Does not contain |
| Language (locale) | Equals · Does not equal |
| Enrolled in course | Equals · Does not equal |
| Has purchased | Equals · Does not equal |
| Opened email / Clicked in email | Exists · Does not exist · Equals · Does not equal |
| Days since signup | Less than |
A tag condition compares the spelling exactly, so write the tag as it appears on your contacts.
An example
- Starts when: Purchase completed
- If Tags contains
customer: she has bought before. Send an email saying you’re glad she’s back. - Else: she’s new. Subscribe her to the welcome sequence and add the
customertag.
That way someone buying again doesn’t get the same welcome email a second time.
What can go inside a branch
A branch of If / Else and a variant of A/B test can hold ten of the fourteen steps: email, tags, courses, sequences, Notify me, Send notification (in-app) and Update contact. Four can’t:
- Wait / Delay
- If / Else, so no branch inside a branch
- A/B test
- Webhook
If you need to wait after a branch, let the branch add a tag and build a new automation that starts on that tag. Two small flows are also easier to debug than one big one.
Wait / Delay
Wait / Delay pauses the flow for a number of days, hours or minutes before the next step. For example:
- Starts when: Course completed
- Wait / Delay: 2 days
- Send email: “What did you think? Here’s the next step.”
Two days after the last lesson, she has had time to take the course in before you ask.
A/B test
The A/B test step splits contacts between two paths. Use it to try two ways of following up. To test two subject lines, use the broadcast instead; see Send broadcasts.
Let the test run until enough people have gone through. Twenty people won’t tell you much.
Chain flows with tags
One automation can add a tag that starts another. That’s how three small automations can work together:
- Automation 1, interest. Starts when: Form submitted → Add tag
interest→ Subscribe to sequence “The free guide” - Automation 2, sell. Starts when: Tag added
clicked-sales-link→ If Tags containsinterest→ Subscribe to sequence “The offer” - Automation 3, customer. Starts when: Purchase completed → Remove tag
interest→ Add tagcustomer→ Enroll in course
Three small automations are easier to understand and fix than one big one.
Avoid loops
If automation A adds a tag that starts automation B, and B adds a tag that starts A, it goes round in a circle. Sketch the flow on paper before you build. If an arrow points backwards, break it with a condition, such as the customer tag must not be there.
Test a flow with branches
- Use your own address as the test contact.
- Choose Test → See what would happen and pick your contact. You see which path she would take, and nothing is sent.
- Start the flow for real, for example by adding the tag to yourself.
- Check that the right email arrived, the right tags were added and you ended up in the right branch. Look under Runs.
- Fix it and try again.
Test one branch at a time, so you have seen every path work at least once.
Tips
- Name tags with a system, such as
interest-yogaandcame-via-free-guide. Conditions then read easily. - Say what the automation does in its name, such as “Part 2 of 3: interest to sale”.
- Add conditions when you find you need them, not before.
