Automation Platform > Triggers & integrations
Triggers overview
# Triggers overview Warp runs cloud agents from Slack, Linear, and GitHub mentions, recurring schedules, or API calls. A trigger starts a run from an event or schedule; use [integrations](/platform/integrations/) to connect the tools your team already uses, or GitHub Actions to run an agent inside your CI workflow. For triggers that route work through one factory's named agents and workflow, use [factory automations](/factories/automations/) and [factory integrations](/factories/connect-your-factory/). To set up your first recurring agent, follow the [Scheduled agents quickstart](/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](/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](/platform/integrations/linear/) | | GitHub | Mention `@warp-agent` in an issue, PR, or review comment, or a new PR description. | Status, progress, and summary in the same thread, including any PRs opened. | [GitHub integration](/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](/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](/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](/platform/oz-web-app/). | [Oz CLI](/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](/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](/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](/platform/managing-cloud-agents/), where you can filter by source, status, day, or creator. ## Related pages * [Integrations overview](/platform/integrations/) - Connect Slack, Linear, GitHub, Jira, and other supported services. * [Run agents unattended with schedules and triggers](/guides/agent-workflows/how-to-run-unattended-agents/) - Choose a trigger for an unattended workflow.Tell me about this feature: https://docs.warp.dev/platform/triggers/Start cloud agents in Warp from Slack, Linear, GitHub, schedules, CI, or API calls, and choose where to inspect their results.
Warp runs cloud agents from Slack, Linear, and GitHub mentions, recurring schedules, or API calls. A trigger starts a run from an event or schedule; use integrations to connect the tools your team already uses, or GitHub Actions to run an agent inside your CI workflow.
For triggers that route work through one factory’s named agents and workflow, use factory automations and factory integrations.
To set up your first recurring agent, follow the Scheduled agents quickstart.
Available trigger types
Section titled “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 |
| Linear | Mention @warp in a comment or assign an issue to the agent. | Updates, summary, and PR links in the Linear issue. | Linear integration |
| GitHub | Mention @warp-agent in an issue, PR, or review comment, or a new PR description. | Status, progress, and summary in the same thread, including any PRs opened. | GitHub integration |
| 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 |
| Schedules | Configure a recurring cron expression and prompt. | Each run’s task and session history, including logs and outputs. | 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. | 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 |
| 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 |
After a trigger fires, track and review the resulting runs across your team from the Agent Management Panel and Oz web app Runs page, where you can filter by source, status, day, or creator.
Related pages
Section titled “Related pages”- Integrations overview - Connect Slack, Linear, GitHub, Jira, and other supported services.
- Run agents unattended with schedules and triggers - Choose a trigger for an unattended workflow.