Build timed follow-up in an automation
Add waits, messages, stopping rules, and event branches to one lifecycle automation.
Available to people with permission to manage the relevant automation.
Timed follow-up lives inside an automation. Older timed-follow-up links open the top-level Automations workspace, and migrated workflows keep their waits, messages, and enabled state.
Available to
Owners and admins can manage every automation. Staff with pipeline access can manage pipeline-scoped follow-up.
Before you start
Draft the complete lifecycle first: who should enter, what events may happen, how long each wait should be, what each message should say, and what should stop further follow-up. Confirm communication authorization before enabling anything that sends to clients or leads.
Steps
- Open Automations and open the pipeline’s default automation or create another pipeline-scoped automation.
- Add the entry trigger and any Only when filters.
- Add the first action, then Wait for duration, Wait until, or Wait for event.
- Continue the path and add branches for replies, bookings, status changes, or timeout.
- Add clear end nodes so enrollment, terminal stages, opt-out, or other stopping events do not continue follow-up.
- Preview a sample record, save while Off, then turn the automation On only after review.
What happens next
New qualifying events can enter the saved automation. Wait nodes pace the journey, and Activity explains what happened.
If you do not see this option
If the pipeline automation or Save is unavailable, ask an owner or admin to review your workflow access and resolve any validation message first.
Last reviewed July 25, 2026
Related articles
Was this article helpful?
Your feedback helps us improve the Help Center.