An automation's timeline is relative — you don't set dates here. Day 1 of week 1 becomes each client's start date when you assign the automation, and everything else follows from there.
A new automation opens with an empty four-week timeline. The editor shows it by week or by month, defaulting to month with four weeks per page, and arrows move between pages or weeks.
Add an event to the timeline
- In the automation editor, click any day.
- Pick the event type from the table below.
- Give the event a name, set its time of day, and fill in the type's details — the program to assign, or the message to send. The message composer includes an emoji picker.
- Click Add Event.
A day can hold any number of events. The time defaults to 9:00 AM, and an event with no time set fires at 9:00 AM.
Automation event types
| Event | What the client gets |
|---|---|
| Add Phased Program | A phased program, with per-program method, delivery, and start choices |
| Add Structured Program | A structured program assigned on that day |
| Add Meal Plan | A meal plan assigned on that day |
| Add One-Time Form | A one-time form to fill in |
| Add Vault Collections | One or more vault collections shared with the client |
| Add Vault Resources | One or more vault resources shared with the client |
| Automated Message | A chat message from you in the client's conversation |
| In-App Notification | A push notification with a title and description you write |
For a phased program you choose the method (Subscribe to the shared program, or Copy it so the client gets their own editable version), the delivery (Schedule places it on the calendar from a start date, On-demand gives it as a dateless library), and the start (that day, or let the client pick). Defaults are Subscribe, Schedule, and that day. With On-demand, the start option doesn't apply.
Event limits
| Field | Limit | When it's checked |
|---|---|---|
| Event name | 100 characters | At save |
| Automated message | 1,000 characters | At save |
| Notification title | 65 characters | As you type |
| Notification description | 178 characters | As you type |
| Vault items per event | At least one | At save |
Edit, move, and delete automation events
- Edit — click the event to change any field, including its content. The event's type can't be switched while editing; delete it and add a new one instead.
- Move or reorder — drag an event to any other day to move it, or drag within its own day to reorder that day's events.
- Delete — click the event and choose Delete.
Manage weeks in an automation
Use Add Week to extend the sequence. Each week also has controls to insert a week after it, clear its events, or delete it. An automation always keeps at least one week, and deleting or inserting renumbers the rest.
Clearing or deleting a week applies immediately with no confirmation. To back out, close the editor without saving.
Save the automation
Nothing is stored until you click Save. Unsaved changes are flagged in the editor header, and closing with unsaved changes shows a warning first.
Things to watch out for
Editing an automation only affects clients you assign it to later. Clients already on it keep the events that were copied to them at assignment time.
Two older event types — check-in forms and on-demand programs — can no longer be added. Automations built before they were retired keep showing and running them, and those events can still be edited. Assign check-in forms directly instead.