> ## Documentation Index
> Fetch the complete documentation index at: https://docs.opencomputer.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Triggers

> Start and resume sessions from external events

<Note>**Labs preview.** Triggers are not part of the stable Durable Sessions API. For stable API access, use [`POST /sessions`](/agent-sessions/api-reference) to start work and [`POST /messages`](/agent-sessions/messaging) to steer it.</Note>

Triggers let external events start or resume sessions. You declare them on an [agent](/agent-sessions/agents); OpenComputer receives events, de-duplicates them, and routes them to a session.

```toml theme={null}
[[triggers]]
type = "github"
on   = "issue.labeled:agent"
```

* **Sources:** GitHub (issue labeled, PR/issue comment) and Slack `@mention`.
* **Routing:** a routing key groups events into sessions — by default one session per issue; a comment on a PR the agent opened resumes the session that opened it.
* **Who can trigger:** restricted to members of your organization by default, configurable per agent.

To fire an agent on a **cron** rather than an external event, use [Schedules](/agent-sessions/schedules) — a time-based trigger with its own stable API.

## Integrations

Triggers and outbound deliveries run through platform integrations, so the agent holds no
GitHub or Slack tokens. [Installing the OpenComputer GitHub App](https://github.com/apps/opencomputerdev/installations/new) configures GitHub access;
Slack channels use a Slack integration.

## Deliveries

To open or update a draft PR, post a comment, or take another external action, the agent
requests a **delivery** and OpenComputer performs it as the org or as the triggering user,
depending on the configured grant. For generic outbound delivery, use
[webhooks](/agent-sessions/webhooks).

See [Channels](/agent-sessions/channels) for the two-way conversation model and [Workspaces](/agent-sessions/workspaces) for the repo a triggered session works in.