Schedules and triggers
Run an agent automatically on a schedule, or start it from another system with a webhook trigger.
By default an agent runs only when someone starts it. A Schedule lets it run on its own at set times, and a webhook trigger lets another system start it.
Scheduled runs are available on Business and Enterprise. On Free the New schedule action is locked and explains why.
Create a schedule
The agent must be deployed, switched on and fully set up first. A draft or an agent that still needs setup cannot be scheduled, because its runs would fail.
Open the Schedule tab
On the agent's page, open Schedule and choose New schedule.
Step 1: What to run
Choose AI agent and select the agent (it may already be selected). Optionally name the schedule. If the agent has run input fields, fill in what each scheduled run starts with. They are the same fields as Run now.
Step 2: When
Pick a preset such as Daily at 09:00, Weekdays at 09:00 or Every Monday 09:00, or enter a Custom cron expression in the form minute, hour, day, month, weekday. Choose the Timezone. The dialog shows the Next 3 run times so you can check it.
Step 3: Options
Choose Retry on failure with a maximum number of retries and a delay, and whether to Notify on failure or Notify on success.
Create schedule
Choose Create schedule.
Under When this fires you can choose Runs directly, which starts the agent immediately, or Creates a board task, which drops a card on the board with this assignee so a board agent picks it up.
Manage schedules
On the Schedule tab each schedule shows whether it is Active or Paused and when the Next run is. You can:
- Pause and resume it.
- Run now to start it once outside its times.
- Open Recent runs to see what it did.
- Delete it. The schedule stops and its history is no longer reachable from here.
Runs that a schedule starts are called scheduled runs and appear in the agent's Results tab, marked scheduled.
A scheduled run is started on behalf of someone. If the agent uses a personal connection that belongs to another person, those actions are skipped. Use workspace-wide connections for scheduled agents. See Actions and connections.
When nobody is watching, an action that asks for approval waits until someone approves, so a scheduled agent that sends email may pause. See Runs and approvals.
Webhook triggers
A webhook trigger gives you a URL that another system can call to start the agent.
Add the trigger
On a deployed agent, open the options menu (the three dots) at the top of the page and choose Add webhook trigger.
Name it
On New webhook trigger, give it a name and choose the agent as target, then Create trigger.
Copy the URL and secret
You see the Webhook URL and the Signing secret once. Store the secret safely: it is not shown again.
The calling system signs each request with the secret, using the headers shown on the page, and requests older than a few minutes are refused. The data it sends is passed to the run as input. All triggers are listed under Triggers, where you can open View fire history.
Managing webhook triggers is limited to workspace admins and team managers.