> For the complete documentation index, see [llms.txt](https://missiveapp.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://missiveapp.com/docs/advanced-features/rules/triggers.md).

# Triggers

Understand rule triggers and when automation runs.

Pick one rule type. This determines when the rule runs.

## Incoming messages

Fires when a message arrives in your inbox from any of these channels:

| Channel         | What it catches                               |
| --------------- | --------------------------------------------- |
| Email           | New emails received                           |
| SMS             | Incoming text messages via Twilio             |
| WhatsApp        | Incoming WhatsApp messages                    |
| Messenger       | Facebook Messenger messages                   |
| Instagram       | Instagram Direct Messages                     |
| Live Chat       | Messages from Missive Live Chat widget        |
| Custom channels | Messages from custom integrations             |
| Post            | Posts created through the API or integrations |

{% hint style="info" %}
Incoming message rules run before the message appears in anyone's inbox. Actions happen instantly.
{% endhint %}

{% hint style="info" %}
**Incoming email rules trigger once per email account**

When multiple email accounts receive the same message (via CC, BCC, or forwarding), incoming email rules run once for each account.

Most actions produce the same result when run multiple times:

* **Add label** - Label appears once
* **Assign user** - Same assignment each time

Some actions produce different results each time:

* **Forward** - Sends the message multiple times, once per account

To control this, add an **Email account** condition to run the rule on only one specific account.
{% endhint %}

## Outgoing messages

Fires when you or a teammate sends a message:

| Channel   | What it catches              |
| --------- | ---------------------------- |
| Email     | Emails sent from Missive     |
| SMS       | Outgoing text messages       |
| WhatsApp  | Outgoing WhatsApp messages   |
| Messenger | Outgoing Facebook messages   |
| Instagram | Outgoing Instagram DMs       |
| Live Chat | Agent responses in Live Chat |

Common uses:

* Auto-assign conversations to the person who replied
* Schedule follow-up reminders
* Apply labels to track sent messages

## User actions

Fires when someone does something in Missive:

| Action                        | When it fires                                |
| ----------------------------- | -------------------------------------------- |
| New comment                   | A comment or task is added to a conversation |
| Label change                  | A label is added or removed                  |
| Conversation closed           | Someone closes a conversation                |
| Conversation reopened         | A closed conversation is reopened            |
| Conversation assignee changed | Assignees are added or removed               |
| Team changed                  | Conversation moves to a different team       |

{% hint style="info" %}
User action rules can fire for any user in the organization, or you can filter to specific people using the **Action initiator** condition.
{% endhint %}

{% hint style="warning" %}
**User action rules only trigger when actual users perform these actions.**

Rules performing these actions (like an incoming message rule adding a label) will not trigger user action rules. Put all your actions in a single rule instead of trying to chain rules together.
{% endhint %}

## Personal vs organization rules

**Personal rules** only fire on your private conversations.

**Organization rules** only fire on conversations shared with that organization.

If you need a rule to work on both, create two rules - one personal, one organizational.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://missiveapp.com/docs/advanced-features/rules/triggers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
