Automations
Get started with automations
See which events can start an automation and what it can do, then build your first flow.
An automation waits for something to happen and then does what you’ve decided. Someone buys, and she gets a tag, is enrolled in the course and receives a welcome email.
Automations are under Automations in the Tools group of the menu. The feature is on from the start.
Automation or sequence?
- A sequence is emails in a fixed order. See Email sequences.
- An automation acts on what she does: conditions, branches, tags, course enrolment, webhooks and email.
If you only need five emails in order, a sequence is enough. If something should happen depending on what she has done, you need an automation.
Build your first
- Go to Automations and click New automation.
- Pick a template under Start from a template if one fits, such as Post-purchase welcome, or start empty.
- Name the automation after what it does. “Welcome new customers” says more than “Automation 3”.
- Choose the event under Starts when and create the automation.
- Click + Add step below the start and choose what should happen. Steps run from top to bottom. Click a step to set it up.
- Click Save, then switch on Active when you’re done.
The builder works on a phone too. There the steps show as a list and their settings open in a panel of their own.
What can start an automation
Money and purchases: Purchase completed · Payment failed · Subscription ended · Trial ending
Courses: Enrollment · Lesson completed · Course completed
People and tags: New member created · Tag added · Tag removed · Inactivity
Email and pages: Email opened · Email clicked · Page visited
Forms and bookings: Form submitted · Booking created · Booking cancelled
Events: Attended a live event · Missed a live event
Trial ending only works when billing is switched on, and is marked that way in the list. For Form submitted you choose which form starts it. Any form means the contact form starts it too.
An automation has one start. If the same steps should run on two different events, make two automations.
Steps
| Step | What it does |
|---|---|
| Send email | An email to the contact. Under Kind of email, choose Delivery (about what she bought or booked) or Marketing, which only reaches people who consented. |
| Subscribe to sequence | Enrols the contact in a sequence. |
| Unsubscribe from sequence | Stops a running sequence for the contact. |
| Add tag / Remove tag | Adds or removes a tag. |
| Enroll in course / Remove from course | Grants or removes access to a course. |
| Update contact | Changes name, language, phone, city, country, notes or subscription status. |
| Wait / Delay | Waits a set time before the next step. |
| If / Else | Splits the flow into a yes branch and a no branch. |
| A/B test | Splits contacts between two paths. |
| Notify me | An email to you. |
| Send notification (in-app) | A notification in the member app. |
| Webhook | Sends data to another service. See Webhooks. |
A first flow
- Starts when: Purchase completed
- Add tag:
customer - Enroll in course: your course
- Subscribe to sequence: your welcome series
Every buyer then gets access to the course, the customer tag and your welcome emails.
Active or paused
The Active switch decides whether the automation reacts to new events. Before it switches on, Studio asks Activate this automation?, in the builder and in the list, because emails and tags then go out for real. If you have unsaved changes, the saved version is what runs, so save first.
A paused automation doesn’t react to new events, but flows that have already started run to the end. Pause it before you change anything substantial.
Runs at the top shows who has gone through the automation and how it went.
Test before you switch it on
Under Test there are two checks that send nothing:
- Check the flow checks that the flow can run, for example that no step is missing its settings.
- See what would happen walks through the steps for a person you choose, without sending email or adding tags.
Then try it on yourself. If it starts on Tag added, add the tag to your own contact and check that the right things happen. If it starts on Purchase completed, make a 10 kr purchase and refund it in Stripe afterwards.
Tips
- Start with one trigger and two steps. Build on it once it works.
- Give the automation a name you’ll understand in six months.
- Always add a tag on purchase. Then your next automation can tell who is a customer.
- Conditions, branches and wait times are covered in Conditions, branches and timing.
