> For the complete documentation index, see [llms.txt](https://docs.fastn.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastn.ai/~/revisions/m0hEPQFsdMhQVmegKM0n/reference/triggers.md).

# Triggers

Triggers start workflows. They're managed separately under **Integrations → Triggers** and consist of three types:

### Webhook triggers

Receive events from external services via HTTP POST.

#### Configuration

| Field                | Required         | Description                |
| -------------------- | ---------------- | -------------------------- |
| **Name**             | Yes              | Trigger identifier         |
| **Description**      | No               | What this webhook receives |
| **Routes**           | Yes (at least 1) | Map payloads to workflows  |
| **Advanced options** | No               | Additional configuration   |

#### Routes

Each route maps incoming payloads to a workflow:

| Field           | Description                                                                 |
| --------------- | --------------------------------------------------------------------------- |
| **Workflow**    | Target workflow (dropdown of active workflows)                              |
| **Key / Value** | JSON filter — only payloads matching this key-value pair trigger this route |
| **Header**      | Optional headers to forward to the workflow                                 |

A single webhook trigger can have **multiple routes**. Different payloads go to different workflows through the same endpoint.

#### Example: Route by event type

```
Route 1: Workflow = "process-orders"     Key = event_type  Value = order.created
Route 2: Workflow = "update-inventory"   Key = event_type  Value = inventory.updated
Route 3: Workflow = "sync-contacts"      Key = event_type  Value = contact.updated
```

### Scheduler triggers

Trigger workflows on a time-based schedule.

#### Configuration

| Field           | Required | Description                                      |
| --------------- | -------- | ------------------------------------------------ |
| **Name**        | Yes      | Trigger identifier                               |
| **Description** | No       | What the scheduler does                          |
| **Schedule**    | Yes      | Frequency configuration                          |
| **Starts at**   | No       | Date/time to begin (leave empty for immediately) |

#### Schedule presets

| Preset       | Configuration                                          |
| ------------ | ------------------------------------------------------ |
| **Interval** | Run every X minutes/hours. Set number + unit dropdown. |
| **Daily**    | Run once per day at a specific time.                   |
| **Weekly**   | Run once per week on a specific day and time.          |
| **Monthly**  | Run once per month on a specific date and time.        |
| **Custom**   | Enter a cron expression for complex schedules.         |

### App Event triggers

Subscribe to events from connected third-party apps.

#### Configuration

| Field          | Required | Description                             |
| -------------- | -------- | --------------------------------------- |
| **Name**       | Yes      | Trigger identifier                      |
| **Connector**  | Yes      | Which connector to listen to (dropdown) |
| **Connection** | Yes      | Which authenticated connection to use   |
| **Event**      | Yes      | Which event to subscribe to             |

#### Event list

The event list shows available events from the selected connector:

| Element                 | Description                                         |
| ----------------------- | --------------------------------------------------- |
| **Event name**          | Human-readable name (e.g., "Sale Created")          |
| **Type badge**          | WEBHOOK — indicates the event mechanism             |
| **Subscription status** | **Not Subscribed** (red) or **Subscribed** (green)  |
| **Event path**          | Technical path (e.g., "Sale/Created")               |
| **Payload Schema**      | Expandable section showing the event data structure |

When you create the trigger, Fastn subscribes to the webhook on the third-party app automatically. Deleting the trigger unsubscribes.

### Trigger management

#### Tabs

| Tab            | Count shown | Contents                      |
| -------------- | ----------- | ----------------------------- |
| **Webhooks**   | e.g., "(0)" | Webhook triggers with routes  |
| **Schedulers** | e.g., "(1)" | Time-based triggers           |
| **App Events** | e.g., "(3)" | Connector event subscriptions |

#### Each tab has

* Search bar
* Status filter ("All statuses")
* Trigger list with edit/delete actions


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fastn.ai/~/revisions/m0hEPQFsdMhQVmegKM0n/reference/triggers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.