> For the complete documentation index, see [llms.txt](https://docs.warp.dev/llms.txt).
> Markdown versions of each page are available by appending .md to any URL.

# Triggers overview

Configure triggers to run cloud agents automatically based on schedules or events.

A trigger is anything that starts a cloud agent run without you typing a prompt: a recurring schedule, an integration like Slack or Linear, a CI event, or a call to the API. This page covers the full set, including the [integrations](https://docs.warp.dev/platform/integrations/) that connect agents to the tools your team already uses.

To set up your first recurring agent, follow the [Scheduled Agents Quickstart](https://docs.warp.dev/platform/triggers/scheduled-agents-quickstart/).

If you’re choosing between schedules, Slack, Linear, GitHub, GitHub Actions, the Oz CLI, or the API, start with [Run agents unattended with schedules and triggers](https://docs.warp.dev/guides/agent-workflows/how-to-run-unattended-agents/).

## Available trigger types

-   **[Scheduled Agents](https://docs.warp.dev/platform/triggers/scheduled-agents/)** - Run agents on a recurring schedule using cron expressions.
-   **[CLI](https://docs.warp.dev/reference/cli/)** - Trigger cloud agents directly from your terminal using the Oz CLI.
-   **[API & SDK](https://docs.warp.dev/reference/api-and-sdk/)** - Programmatically trigger agents via the Warp API or SDK.
-   **[Integrations](https://docs.warp.dev/platform/integrations/)** - Trigger agents from external services like Slack, Linear, or Jira.
-   **[GitHub](https://docs.warp.dev/platform/integrations/github/)** - Mention `@warp-agent` on an issue, pull request, or review comment to start an agent that replies in the thread.
-   **[GitHub Actions](https://docs.warp.dev/platform/integrations/github-actions/)** - Run agents from your own CI workflows and repository events.
-   **[Custom webhooks](https://docs.warp.dev/factories/webhooks/)** - Give a [factory](https://docs.warp.dev/factories/) an authenticated URL that any system can POST JSON to, and start its automations from the deliveries.

After a trigger fires, track and review the resulting runs across your team from the [Agent Management Panel and Oz web app Runs page](https://docs.warp.dev/platform/managing-cloud-agents/), where you can filter by source, status, day, or creator.