Visual Automations Actions
What Is An Action?
Actions are very polite, and they wait until the previous step has completed, then direct the subscriber to the next step in the automation. Just like when you go out to eat, and you have to wait for the party ahead of you to vacate the table, before you sit down, an action will wait until the previous step has finished before it will usher subscribers ahead.
They are indicated by a green color, so just think “Ok it’s time to go again”. There are several types of actions for each automation:
- Add the subscriber to a sequence.
- Add the subscriber to a tag.
- Remove a tag
- Delay the subscriber.
Some examples of Actions… in action
A subscriber completes a sequence, add a tag that they finished the sequence.
Takeaway: Actions are patient, but then only direct a specific way. Basically, “this is happening”.
A real life example of this would be going to a theme park. Once you finish one ride, you go wait in another line, and then start the next ride. All of these are direct actions that wait for the previous step to be completed.
Remove a Tag
Now you can remove a tag from a subscriber, just like you can add one. This will check if the subscriber has a specified tag and remove it if they do.
ConvertKit Hint: Delays are useful if you want subscribers to wait for something else to complete, or simply to give them a “break” before something else happens. This can be helpful if you are surveying your audience to see what topic they are interested in.
We do this too!
We use this technique at ConvertKit to onboard new customers. In the first email there are two links, “New to Email Marketing” and “Experienced”. Since people don’t always open emails right away, we built in a two day delay at the end of the sequence to give people a little extra time to re-open and click the link. Here’s a look at how a finance blogger may use delays also.
3 More Action Possibilities
To find these three options, you'll click on Move Subscriber:
Once you click on Move Subscriber, you'll see three options.
This allows you to remove a subscriber from the current automation. It acts the same as the final “END OF AUTOMATION” node. This is only available in Condition branches or Events when there are multiple in the same row. There has to be another path a subscriber can take for this to work.
Once you add this node, you will notice the line ends there because subscribers can’t move past it:
Add to another automation
This allows you to add a subscriber to the beginning of another automation. They would remain in both automations. Multitasking like a pro!
An entry node will show up in that automation to show the number of subscribers who have entered via another automation. This node would only show up once a subscriber actually took this path.
Remove from another automation
This action will check if the subscriber is currently in another automation and if so remove them. This is handy for making sure subscribers are not in 2 overlapping automations at once, when moving them around!
- Actions are polite, waiting for the previous step to be completed.
- Actions direct subscribers to the next indicated step.
- Actions can add a tag, start a sequence, or add a delay.
- Actions can remove a tag, add a subscriber to an automation, or cause them to exit an automation
Up Next: Visual Automations, Conditions! Click to read
Still feeling lost?