> For the complete documentation index, see [llms.txt](https://docs.ebbot.ai/ebbot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ebbot.ai/ebbot-docs/core-capabilities/automations/workflow-nodes/trigger-nodes.md).

# Trigger Nodes

## **Trigger nodes** <a href="#id-1.-trigger-nodes" id="id-1.-trigger-nodes"></a>

**Purpose**: Start a workflow when a specific event occurs

**Characteristics:**

* Every workflow must have at least one trigger
* Triggers listen for external events
* Each trigger provides a **payload** with event data accessible to all nodes

**Available triggers:** triggers are provided by **Integrations**. As new integrations are installed, the library of available triggers grows.

* **Native triggers**: Core triggers like **Cron** come from the **Core Utilities** integration.
* **Integration triggers**: Provided by installed apps (e.g., "New Zendesk ticket", "Email received", "Status changed").
* **Extensible architecture**: Since integrations are standalone services, a trigger can be anything that can interact with a web server.