# Trigger reference

Every flow begins with one **trigger**, which starts the flow, ingests the initial input, and injects it as normalized data for downstream nodes. This page is a compact reference to every trigger visible in the builder and its availability. For how to set up the available triggers, see [Configure triggers](../build-ai-agents/triggers.md).

## Trigger availability

Only triggers marked **Available** can be configured and used today. The others are visible in the builder but cannot be set up.

| Trigger | Purpose | Input source | Availability |
| --- | --- | --- | :---: |
| Manual File Upload | Start a flow by uploading files by hand | Files you upload | **Available** |
| Outlook Trigger | Start a flow when a matching email arrives | A connected Outlook mailbox | **Available** |
| HTTP Trigger (Webhook) | Start a flow from an inbound webhook | — | Not available |
| Recurring Schedule or Timer | Start a flow on a schedule | — | Not available |
| SFTP Trigger | Start a flow when files arrive over SFTP | — | Not available |

## Available triggers

### Manual File Upload

- **Purpose:** start a flow by uploading one or more files directly. Best for building and testing, and for ad-hoc, on-demand processing.
- **Input source:** files uploaded by a person.
- **Injected data:** each uploaded file's name, type, size, and identifier, plus a count of the files. Downstream nodes such as Read Files begin from this.
- **Configuration summary:** Allowed File Types; Maximum File Size (1–100 MB); Maximum Number of Files (1–20).
- **Setup:** [Configure triggers — Manual File Upload](../build-ai-agents/triggers.md#manual-file-upload).

### Outlook Trigger

- **Purpose:** start a flow automatically when an email arrives in a connected mailbox. The common entry point for processes that begin with inbound email, such as broker submissions or claims correspondence.
- **Input source:** a connected Outlook mailbox, authorized through the Outlook authentication integration. See [App integration nodes](../build-ai-agents/app-integration-nodes.md).
- **Injected data:** the email and its key details (subject, sender, whether it has attachments), with the message and attachments made available to downstream nodes such as Download Outlook Email.
- **Configuration summary:** Event Type (Message Created / Updated / Deleted); Enabled; optional Filters (Field — Subject / Sender / Has Attachments; Operator — Contains / Equals / Starts With / Ends With / Regex; Value; Case Sensitive). Multiple filters must all match.
- **Setup:** [Configure triggers — Outlook Trigger](../build-ai-agents/triggers.md#outlook-trigger).

## Not-available triggers

**HTTP Trigger (Webhook)**, **Recurring Schedule or Timer**, and **SFTP Trigger** appear in the builder but are **not available** and cannot be configured. They are listed here for visibility only; they have no setup steps until they are enabled. Do not plan production intake around them.

## Starting runs programmatically

Separate from the trigger nodes above, a published flow can be run from another system through the [Bevaya API](/api) with `POST /flows/{flowId}/run`. This is the released way to start runs programmatically — for example, from an existing intake system — and complements the Outlook Trigger for production. See [Start a flow run](/api/flow-executions#run-a-flow).

## Where to go next

- [Configure triggers](../build-ai-agents/triggers.md) — full setup steps for the available triggers.
- [Node catalog reference](./node-catalog.md) — the nodes you connect after the trigger.
- [App integration nodes](../build-ai-agents/app-integration-nodes.md) — set up the Outlook mailbox connection.
- [Start a flow run](/api/flow-executions#run-a-flow) — start runs through the API.