Build and activate an automation
Build one connected workflow with triggers, waits, branches, and actions, then turn it on when it is safe to run.
Available to people with permission to manage school or pipeline automations.
Build one connected automation for a lifecycle, including every event, wait, branch, and action that belongs together.
Available to
Owners and admins can manage every automation. Staff with pipeline access can manage pipeline-scoped automations. Other internal staff can review the activity their access allows.
Before you start
Write down the lifecycle, its possible entry events, the events that resume a waiting journey, and the intended outcomes. Timed follow-up is built with wait and message nodes inside the same automation; there is no separate Drip type.
Steps
- Open Automations.
- Select New automation.
- Start blank or choose a relevant template, then give it a short name.
- Add one or more trigger nodes. Put optional filters under Only when.
- Add waits and conditions, including a Timed out path when a wait should not continue forever.
- Add actions and review every recipient, stage, tag, owner, report, and message.
- Resolve validation shown on nodes and fields.
- Use Preview with a sample record. Preview renders the path and messages without sending or writing anything.
- Save while the automation is Off and review its Activity panel.
- Turn it On only when the workflow and every provider/permission gate are ready.
What happens next
The automation begins responding to new matching events. Open Activity to see plain-language outcomes, waiting journeys, skipped sends, and remediation actions.
If you do not see this option
If New automation, On, or Save is unavailable, ask an owner or admin to review your access and fix any validation message first. Domain actions still enforce their own scheduling, billing, messaging, report, and pipeline permissions.
Last reviewed July 25, 2026
Related articles
Was this article helpful?
Your feedback helps us improve the Help Center.