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

# Triggers

> Start one workflow automatically when another workflow's data changes

Triggers start one workflow automatically when something happens to another's data — no manual run or external scheduler. Chain workflows, like a downstream extraction whenever an upstream one finishes or its data changes.

<img src="https://mintcdn.com/kadoa/6ptQX_ORLvflLYsp/images/workflows/triggers.png?fit=max&auto=format&n=6ptQX_ORLvflLYsp&q=85&s=ef1ea022382fa9710dd00104ad9b5dca" alt="Workflow triggers" width="2784" height="1774" data-path="images/workflows/triggers.png" />

## Create a trigger

1. Open a workflow → **Triggers** tab → **Add trigger**.
2. Choose when it fires:
   * **Data changed** — data changed between runs
   * **Workflow finished** — a run completed
   * **Export completed** — an export finished
3. Select the workflow to run → **Create trigger**.

The target runs the next time the event fires. Toggle a trigger off to pause it without deleting.

## What you'll see

* Workflows with triggers show a lightning icon and count in the dashboard table.
* The **Triggers** tab lists outgoing triggers and, below, incoming triggers (workflows that start this one).

## Limits

* Up to 5 triggers per workflow.
* A workflow can't trigger itself.
* Realtime workflows can't be targets.
* Source and target must share the same team (or the same user for personal workflows).
* A triggered run only starts if the target is active, not already running, and has no open support issue. Events that arrive mid-run are skipped, not queued.
* Chains up to 5 levels deep to prevent loops.

For time-based runs, see [Scheduling](/docs/ui/workflows/scheduling). To get notified of these events instead, see [Notifications](/docs/notifications).
