# Schedules

A schedule runs an agent automatically — on a cadence, on an event, or on an inbound webhook. Here's how to create one, choose its trigger, and switch it on.

## Create a schedule

- 01Open SchedulesIn the Workbench, go to Automation → Schedules and click New schedule. The full-page schedule editor opens.New scheduleAutomation → Schedules → New schedule.
- 02Name it and pick who runsGive the schedule a clear name — e.g. Morning inbox sweep — and choose the agent or crew that runs when it fires. Crews run at their tier (Fast, Premium, or Max); see Building agents.
- 03Choose a triggerThe trigger decides what starts the run. Pick one:Schedule — a recurring cron cadence, e.g. Daily · 8:00 or Mon · 9:00.Event — an internal signal, e.g. a file change.Webhook — an inbound HTTP call, e.g. GitHub · pull_request.Trigger · Schedule / Event / WebhookThe trigger picker in the schedule editor.
- 04Set the cadenceFill in the cadence for the trigger you chose — the timing for a Schedule, the event name for an Event, or the hook for a Webhook. Next run shows when it’s due to fire next.
- 05Enable itFlip the Enabled switch on and save. A disabled schedule is kept but never fires — handy for pausing without losing the setup. You can also toggle a schedule straight from its row in the list.EnabledToggle a schedule on or off from the editor or the row.

## How triggers map to runs

Every trigger carries the instruction the agent gets when it fires — the prompt that the run starts from. A cron schedule fires on its cadence in your timezone; an event fires when its topic is signalled; a webhook fires on the inbound call. Channels can be the source of those events — see Channels.

> Triggers are authored, not yet fully drivenYou can create and enable any trigger type today, but the executor that fires them unattended is still being wired up. Use schedules to model the automation you want; don’t rely on one running on its own just yet.