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


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ebbot.ai/ebbot-docs/core-capabilities/automations/workflow-nodes/trigger-nodes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.