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

# Workflow Triggers

Triggers are an advanced automation feature that starts workflows automatically when specific events occur in connected applications. When the configured event fires — such as a record creation, a status change, or a threshold being reached — the workflow runs immediately, with no manual action required.

Triggers are configured in the Start node and can be used alone or combined with the Scheduler.

***

## How Triggers Work

1. A trigger listens for real-time events from an integrated third-party app.
2. When the event occurs, the workflow starts immediately.
3. Event data — including metadata and attachments — is passed into the workflow for downstream processing.

<img src="https://mintcdn.com/koreai/SI3fhJbLrkAy7jPS/ai-for-process/workflows/images/triggers.png?fit=max&auto=format&n=SI3fhJbLrkAy7jPS&q=85&s=ecde19f0613c1d49ff85dc44a3dcdd38" alt="Triggers" width="1920" height="862" data-path="ai-for-process/workflows/images/triggers.png" />

***

## Prerequisites

Before adding a trigger to a workflow:

* Add the integration app to your workspace.
* Set up the required connection and authentication profile.
* Open the workflow in Flow Builder and access the **Start node**, where all triggers are configured.

For configuration steps, see [Start Node – Automate Workflow Initiation](/ai-for-process/nodes#start-node).

***

## Trigger Payload and Attachments

| Topic                  | Details                                                                                    |
| ---------------------- | ------------------------------------------------------------------------------------------ |
| **Contextual data**    | Triggers can pass event-specific metadata, IDs, and contextual data into the workflow.     |
| **Attachments**        | Provided as temporary URLs valid for 24 hours. Only one attachment is supported at a time. |
| **Workflow variables** | Downstream nodes can reference trigger payload fields as workflow variables.               |

## Best Practices

* Use clearly defined events to avoid unnecessary workflow runs.
* Validate integration connections regularly to keep triggers active.
* Confirm payload fields before referencing them in conditions or expressions.
* Monitor trigger activity to quickly identify and fix inactive or failing triggers.

***