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.

Trigger availability

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

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.
• Accepted files: see Supported file types for what can be manually uploaded.
• Setup: Configure triggers — Manual File Upload.

API Trigger

• Purpose: start a flow from another system by calling the Bevaya API directly. The released way to trigger runs programmatically, for example from an existing intake system.
• Input source: another system, via a POST /flows/{flowId}/run call to the Bevaya API.
• Setup: not configured in the builder — see Start a flow run in the API reference for the endpoint and request format.

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.
• 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.

Coming Soon triggers

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

Where to go next

• Configure triggers — full setup steps for the available triggers.
• Node catalog reference — the nodes you connect after the trigger.
• App integration nodes — set up the Outlook mailbox connection.
• Start a flow run — start runs through the API.