# Triggers

> Run an agent on a schedule, on a webhook, or on an event in a connected app.

Source: https://docs.runbear.io/triggers

Last updated: 2026-08-26

A deployed agent normally waits to be mentioned. A trigger runs it without anyone
asking: every weekday at 9am, when a webhook arrives, or when something happens in
an app you have connected.

Triggers live on the **Event Triggers** tab of an agent.

## Before you begin

- An agent with at least one channel connected, so its output has somewhere to go.
- For app events, the relevant tool connected on the [Tools](/agents/tools/overview.md)
  tab. The trigger picker recommends events from apps the agent already uses.

## Creating a trigger

Select **Add Event Trigger** and choose when it should run:

| Type               | When it fires                                          |
| ------------------ | ------------------------------------------------------ |
| **On Schedule**    | A recurring cadence: hourly, daily, weekly, or monthly |
| **One-time**       | Once, at a date and time you pick                      |
| **HTTP / Webhook** | Whenever a request arrives at the generated URL        |
| **App event**      | When the chosen event happens in a connected app       |

Then write what the agent should do when it fires. The trigger carries a prompt,
so the same agent can behave differently depending on what woke it up: a Monday
digest, a reply to an incoming ticket, an alert summary.

App-event triggers also accept a filter, so the agent runs only on the events that
matter rather than on every one the app emits.

## Limits

Each plan allows a number of triggers per organization and a number of trigger
runs per day. The tab shows both counts against your limits, and the **Add Event
Trigger** button is disabled once the trigger limit is reached.

## Related

- [Tools](/agents/tools/overview.md) — connect the app whose events you want to use
- [Channels](/channels/slack.md) — where a triggered run posts its result
- [Traces API](/api/traces.md) — inspect what a triggered run did