Triggers & schedules
Decide what starts an execution — on a schedule, conversationally, or from your code.
A trigger is what starts an execution of a deployed agent or workflow. Compass supports a few ways to kick one off, with more on the way.
Schedules
A schedule runs a deployment automatically on a recurring timetable. You manage schedules on a deployment's Triggers tab.
To add one, use the schedule builder:
Pick a frequency
Hourly, daily, weekly, or monthly.
Set the timing
Choose the time of day (in UTC), and the days of the week or day of the month where it applies.
Confirm
A plain-language preview (for example, "At 09:00, Monday through Friday") shows exactly when it will fire before you add it.
Existing schedules are listed with both that human-readable description and the underlying cron expression, and each can be paused, resumed, or deleted. Pausing a deployment suspends all of its schedules at once.
Schedules run in UTC
Times are set and shown in UTC, so a schedule fires at the same absolute moment regardless of where your team is.
Conversationally
You can run a deployed agent or workflow on demand through Compass Chat — enable it in the chat's tool picker and ask it to do its job. This is the quickest way to run something interactively.
From your code
You can trigger executions programmatically through the API, which is the right path for integrating Compass into your own systems. See API, CLI & SDK.
What's coming
Coming soon
Additional trigger types are planned but not yet available in the UI:
- Run now — a one-off manual execution from the deployment page.
- Webhooks — start an execution from an incoming HTTP request.
- Events — start an execution when a matching event occurs.
Seeing how an execution started
Every execution records what triggered it — Scheduled, Manual, or (for ad-hoc executions while building) Test — and shows it as a label in Observability. This makes it easy to tell an automated execution from one someone kicked off by hand.