> 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

Start cloud agents in Warp from Slack, Linear, GitHub, schedules, CI, or API calls, and find where each trigger reports its results.

Warp uses triggers to start cloud agent runs from events or recurring schedules. Choose Slack, Linear, GitHub, GitHub Actions, schedules, the CLI, or the API based on where your work starts.

For triggers that route work through one factory’s named agents and workflow, use [factory automations](https://docs.warp.dev/factories/automations/) and [factory integrations](https://docs.warp.dev/factories/connect-your-factory/).

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

## Available trigger types

| Trigger | How you invoke it | Where to inspect results | Setup |
| --- | --- | --- | --- |
| Slack | Mention `@Warp` in a message or thread, or DM the bot. | Progress, summary, and PR links in the Slack thread. | [Slack integration](https://docs.warp.dev/platform/integrations/slack/) |
| Linear | Mention `@warp` in a comment or assign an issue to the agent. | Updates, summary, and PR links in the Linear issue. | [Linear integration](https://docs.warp.dev/platform/integrations/linear/) |
| GitHub | Mention `@warp-agent` in a new issue comment, pull request comment, review comment, or new pull request description. | Status, progress, and summary in the same thread, including any PRs opened. | [GitHub integration](https://docs.warp.dev/platform/integrations/github/) |
| GitHub Actions | Define repository events and an `oz-agent-action` step in workflow YAML. | Agent output in workflow steps; comments or branches depend on your prompt and permissions. | [GitHub Actions](https://docs.warp.dev/platform/integrations/github-actions/) |
| Schedules | Configure a recurring cron expression and prompt. | Each run’s task and session history, including logs and outputs. | [Scheduled agents](https://docs.warp.dev/platform/triggers/scheduled-agents/) |
| CLI | Start a cloud run from your terminal with the Oz CLI. | Run status and session links from the CLI or [Oz web app](https://docs.warp.dev/platform/oz-web-app/). | [Oz CLI](https://docs.warp.dev/agents/cli/oz-cli/) |
| API and SDK | Submit a prompt and configuration to the Agent and run endpoints. | Run details and session links fetched through the API. | [Agent and run endpoints](https://docs.warp.dev/factories/api-and-sdk/) |
| Custom webhooks | POST JSON to a factory webhook URL; a matching automation starts work. | Delivery log and factory runs; webhooks do not provide thread replies. | [Custom webhooks](https://docs.warp.dev/factories/webhooks/) |

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.

## Related pages

-   [Integrations overview](https://docs.warp.dev/platform/integrations/) - Connect Slack, Linear, GitHub, [Jira](https://docs.warp.dev/platform/integrations/jira/), and other supported services.
-   [Run agents unattended with schedules and triggers](https://docs.warp.dev/guides/agent-workflows/how-to-run-unattended-agents/) - Choose a trigger for an unattended workflow.