# Triggers

A trigger is an event that starts a flow. A trigger can either be an event that occurs within MessageBird or an event that occurs within an external [connector](/applications/integrations/integrations.md).

<figure><img src="/files/kvGjrPH0Gt3N5F6RlLFK" alt=""><figcaption></figcaption></figure>

## Trigger types

There are eight types of trigger:

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Agent</strong></td><td>Run a flow when an agent's availability changes.</td><td></td><td><a href="/pages/2rWYYLWgg8KPi8c1QXXM">/pages/2rWYYLWgg8KPi8c1QXXM</a></td></tr><tr><td><strong>Connector</strong></td><td>Run a flow when an event happens in an installed connector.</td><td></td><td><a href="/pages/ogypwhSa4qF1xDUHglr4">/pages/ogypwhSa4qF1xDUHglr4</a></td></tr><tr><td><strong>Contact</strong></td><td>Run a flow when a contact profile is created, updated, or deleted.</td><td></td><td><a href="/pages/EvS8w5wL79YnjTaytUIq">/pages/EvS8w5wL79YnjTaytUIq</a></td></tr><tr><td><strong>Conversation</strong></td><td>Run a flow when an Inbox conversation is created or updated</td><td></td><td><a href="/pages/O0lAJWYKYo1m6GA6ctOJ">/pages/O0lAJWYKYo1m6GA6ctOJ</a></td></tr><tr><td><strong>Feed item</strong></td><td>Run a flow when an Inbox conversation is created, assigned, archived, or closed.</td><td></td><td><a href="/pages/N8iNdNbO0QlMTg3OaGHC">/pages/N8iNdNbO0QlMTg3OaGHC</a></td></tr><tr><td><strong>Message lifecycle</strong></td><td>Scan, filter, and configure message payloads for better deliverability rates and for content redaction.</td><td></td><td><a href="/pages/3gUn3tXo0mPJcvROSjZz">/pages/3gUn3tXo0mPJcvROSjZz</a></td></tr><tr><td><strong>Webhook</strong></td><td>Run a flow using a webhook when data is pushed to MessageBird.</td><td></td><td><a href="/pages/8Qn7cJ3gPcLglUEC2bM7">/pages/8Qn7cJ3gPcLglUEC2bM7</a></td></tr><tr><td><strong>Voice</strong></td><td>Run a flow when a Voice event happens.</td><td></td><td><a href="/pages/Eqh4zsHNzoBvfNY2SrZk">/pages/Eqh4zsHNzoBvfNY2SrZk</a></td></tr></tbody></table>

## Set up a trigger

### Choose your flow trigger and trigger event

1. On the side panel, click **Flows**.
2. In the top right-hand corner, click the **New flow** button.

<figure><img src="/files/g73lCMXJWvT5sZe6ksGW" alt=""><figcaption></figcaption></figure>

3. Select the trigger types.&#x20;
4. Depending on the trigger you choose, you may need to select a channel instance or a connector to use with the trigger.
5. Select one of the trigger events. This is the specific event that will cause your flow to run.

<figure><img src="/files/O1dGQYnJCGkMYm03uWfM" alt=""><figcaption></figcaption></figure>

6. Click **Save.**

### Test your trigger

Perform the event that will cause your flow to run, then click **Update test data**. MessageBird will attempt to find a recent event from your trigger to use in the flow.

For example, if you set up your trigger to run when a new message is sent to your business' WhatsApp number, send a message to that number, then click **Update test data**.

The information from the message you sent to your business WhatsApp number will be pulled in and displayed in the test window.&#x20;

The data from your test can be used in actions later on in the setup of your flow.

You can also choose to **Skip test**.

<figure><img src="/files/4LKNDX9cDecEGrWWqWdC" alt=""><figcaption></figcaption></figure>

Once you've set up your trigger, continue to build your flow by [adding actions](/applications/automation/flows/concepts/actions.md).


---

# 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.bird.com/applications/automation/flows/concepts/triggers.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.