scheduled) is fired on a recurring schedule instead of by a person. The canonical use:
on a recurrence, iterate a saved View of contacts and fire a contact event for each
one — e.g. “every weekday at 9am, send a renewal reminder to every contact in the
expiring soon view”.
Schedule
The schedule lives in the template’s config:| Field | Required | Description |
|---|---|---|
rrule | Yes | An RFC 5545 recurrence rule (the pattern). |
timezone | Yes | The timezone the rule is evaluated in (DST-aware). |
starts_at / ends_at | No | An optional active window around the recurrence. |
publishing_window_id | No | Optionally fill the window from a Publishing Window. |
Load View
The flow uses a load View node, which counts a saved contacts View and fires a contact event per record, streaming page by page so it stays memory-bounded. The referenced contact event must be enabled and sessionless (a scheduled run has no authenticated contact). Each record’s automation runs independently.Filling
starts_at / ends_at from a Publishing Window
keeps the link live: changing the window’s dates updates every linked schedule.
Editing the dates by hand breaks the link.Available actions
These action plugins can run in a scheduled event:Webhook
Set insight
Send email
Send email to contacts
Related
Event types
All four types compared.
Publishing Windows
Reusable date ranges for the schedule.