Scheduled Run Trigger
A Scheduled Run fires an existing flow automatically on a timer — with no one opening a chat. Use it for reminders, recurring digests, follow-up campaigns, or any flow that should run on its own. A scheduled run (also called an automation) binds one flow to a trigger time and runs it when that time arrives.
Unlike the channel and webhook triggers, a scheduled run is set up outside the flow builder, in the Automations area — you pick the flow, the schedule, and how it should run.
Scheduled runs are managed in the Automations section, not on the Start node's canvas. This page explains the trigger; see Automations for the full management experience.
When it fires
There are two trigger types:
| Trigger type | Fires | You configure |
|---|---|---|
| One-shot | Exactly once, at a future moment | The fire time and timezone |
| Recurring | On a repeating schedule | A cron pattern and timezone |
A one-shot fires exactly once — whether it reaches its scheduled time on its own or you trigger it early with Fire Now. Triggering early consumes the schedule, so it never double-fires. A recurring automation keeps going, advancing to its next occurrence after each fire.
Adding a scheduled run
- Open the Automations area and create a new automation.
- Pick the flow to run (it must belong to your workspace).
- Choose One-shot (set a date/time) or Recurring (set a schedule).
- Set the timezone the schedule is interpreted in.
- Save — the automation is armed and fires when due.
Key settings
| Setting | Description |
|---|---|
| Flow | The AgentFlow to run when the timer fires. |
| Trigger type | One-shot (single future run) or Recurring (repeats on a schedule). |
| Schedule | The fire time (one-shot) or repeating pattern (recurring). |
| Timezone | The timezone your schedule is read in (e.g. Europe/Istanbul). |
| Catchup window | If the system is delayed past this many minutes, that fire is skipped rather than run late. |
| Overlap policy | What to do if a previous run is still going: skip, queue, or run in parallel. |
Times are always interpreted in the timezone you set. Pick your business timezone so "9:00 AM daily" means 9:00 in your local time, not UTC.
Lifecycle
An automation moves through clear states you can see and control:
| Status | Meaning |
|---|---|
| Active | Armed — it will fire when due. |
| Paused | Paused by you — resume to re-arm. |
| Paused by system | Auto-paused by a safety mechanism (e.g. repeated failures). |
| Completed | A one-shot fired successfully — terminal. |
| Cancelled | Stopped by you — terminal. |
You can pause, resume, cancel, or Fire Now at any time. Each fire is recorded in the automation's fire history.
Example
A daily morning digest: pick your digest flow, set Recurring at 9:00 AM in your timezone, and save. Every morning the flow runs on its own, generates the digest, and sends it — no one has to trigger it.
Tips
- Use one-shot for a single future action (a scheduled reminder) and recurring for anything that repeats.
- Raise the catchup window for jobs that tolerate a late run; lower it for time-sensitive sends.
- To send to many recipients from a list on each fire, use a Batch Run instead.