Scheduler
Run a workflow on a schedule
Configure a Scheduled trigger for once, daily, weekly, or monthly workflow starts.
Automation buildersBeginnerAvailable
What this guide covers
- A Scheduled event inside Workflow Trigger starts a full workflow on the configured cadence.
- Prerequisites: A workflow draft.
- Result: Test identifies the Scheduled trigger and the active workflow starts at a future occurrence.
- Limit: The builder exposes UTC, Dubai, London, and New York timezone choices. It does not expose weekday-only, end-date, pause-schedule, or arbitrary cron controls.
What this is and when to use it
A Scheduled event inside Workflow Trigger starts a full workflow on the configured cadence.
| Use it when | Expected outcome |
|---|---|
The scheduled task has multiple nodes. | Test identifies the Scheduled trigger and the active workflow starts at a future occurrence. |
You need daily, weekly, or monthly recurrence. | Test identifies the Scheduled trigger and the active workflow starts at a future occurrence. |
Before you begin
- A workflow draft.
- A selected time and supported timezone.
- Explicit sender and recipient configuration for message nodes because no inbound conversation supplies them.
Prerequisites
A workflow draft. A selected time and supported timezone. Explicit sender and recipient configuration for message nodes because no inbound conversation supplies them.
Complete the task
- Open the workflow and select Workflow Trigger.
- Add a Scheduled event.
- Choose once, daily, weekly, or monthly.
- Set time and timezone; complete any schedule-specific day/date field shown by the builder.
- Configure downstream message nodes with Send From Number and Send To Number.
- Save, Test, and activate.
Confirm it worked
- Test identifies the Scheduled trigger and the active workflow starts at a future occurrence.
Common problems
| Symptom | What to check |
|---|---|
Message node lacks recipient | Scheduled triggers do not provide an inbound sender/recipient context; configure the overrides. |
Occurrence is shifted | Review the trigger timezone rather than assuming the browser timezone. |
Current limitations
The builder exposes UTC, Dubai, London, and New York timezone choices. It does not expose weekday-only, end-date, pause-schedule, or arbitrary cron controls.
Product boundary
The builder exposes UTC, Dubai, London, and New York timezone choices. It does not expose weekday-only, end-date, pause-schedule, or arbitrary cron controls.
Where to go next
Related documentation
Workflow TriggerDefine what starts this workflow. Exact configuration, outputs, execution behavior, errors, limits, and examples for the Workflow Trigger workflow node.DelayWait before continuing. Exact configuration, outputs, execution behavior, errors, limits, and examples for the Delay workflow node.Test a workflowRun a saved workflow with test contact and trigger data while preventing message, database, and external side effects.