Automations can consist of a combination of several steps, but each must have at least one Action step.
Automations can be in one of the following states, which are displayed as tabs in the UI:
Automations that are currently being processed, or have been paused during processing. Active automations can no longer be edited. You can, however archive a paused automation.
Automations that are complete, but with a start date some time in the future. Ready automations can be edited up until the date and time that they are to be run.
Automations that have been created, either in part or completely, but are not ready or have not yet been activated, for whatever reason. Draft automations can be edited at any time and have no impact on deliveries, until they are saved as either Ready or Active.
Automations that have either reached their end date, or have been manually terminated. Archived automations cannot be edited. However, you can clone an Archived automation if, for example, you need to use a copy of it again.
Automations that have resulted in an error while creating a delivery during an Action > Send Email step.
You can define an automation to take place as follows:
If it is not saved as a Draft, the automation is activated immediately after it has been saved.
- In date range
The automation will be active between the defined dates. If it is not saved as a Draft, it is stored as Ready until the start date.
- From date
The automation will be active from the defined date, until it is stopped manually. If it is not saved as a Draft, it is stored as Ready until the start date.
You can define any number of automation steps. The first one is always a Source step, which Is currently defined by default in the UI. Other steps can be of the following types:
An Action is used to configure and instigate an activity that is sent to an external system, for example, to Contactsend for an email delivery. Every automation must have at least one of these. Multiple actions can be used, for example, to send different emails to the same list of contacts, with the appropriate delay between each delivery.
See Adding an Action step for more details.
Currently, the available action is Send Email.
A Check step effectively subdivides an automation into a YES and a NO path and waits for a Trigger event to happen, or not. There are two types of step:
- Wait for Trigger
Pauses the automation until the selected Trigger event takes place. If the event does not happen within a defined time frame, the NO path is taken.
- Wait and Check
Pauses the automation for a defined period of time, then checks to see whether the selected Trigger event has taken place. If the event has not happened after the defined period, the NO path is taken.
- Wait for Trigger
See Adding a Check step for more details.
This adds a delay following the previous step. It can be used, for example, to define a delay between two emails. You can also begin an automation with a Delay if, for example, you want to wait before sending an email, for whatever reason.
See Adding a Delay step for more details.
This is used to complete the automation or a Check path. Once you have added an End step, you can only add further steps before it, not after.
This step is mandatory. If you do not set it, it is automatically added when you save the automation.
See Adding an End step for more details.
Adding contacts to an automation
You can add contacts to an automation in the following ways:
- Create a plan in Contactplan, and apply the Contactflow List Creator option in the plan’s Action section.
See Adding contacts to an automation using Contactplan for more details.
- Use the Add customer API utility.
This enables you to add individual contacts or a group of them to an automation. See the Contactplan API documentation for more details.
- Creating an automation
- Editing an automation
- Adding contacts to an automation using Contactplan
- Viewing automation step analytics and statistics