# Automation

Rules that take action without human involvement.

## Add warning notes for special customers

**Rule type:** Incoming message

Flag conversations with customers who need special handling.

<div data-with-frame="true"><figure><img src="/files/5JLMJrx7K3cZAUcMwWaN" alt="Auto-add note rule" width="617"><figcaption></figcaption></figure></div>

| Component | Value                                                            |
| --------- | ---------------------------------------------------------------- |
| Condition | **From** ends with "acme.com"                                    |
| Action    | **Add note** → "ACME requires background checks on all drivers." |

Notes are visible to your team only, not the customer.

## Show VIP instructions

**Rule type:** Incoming message

Display handling instructions when a VIP contacts you.

<div data-with-frame="true"><figure><img src="/files/xXI0OCBd0VYFQP07tF9h" alt="VIP instructions rule" width="563"><figcaption></figcaption></figure></div>

| Component | Value                                                                                          |
| --------- | ---------------------------------------------------------------------------------------------- |
| Condition | **From** is in contact group "VIP"                                                             |
| Action    | **Add note** → "Priority customer. Escalate immediately if issue is unresolved within 1 hour." |

## Forward receipts to accounting

**Rule type:** User actions → Label change

When someone labels an email as a receipt, forward it to the accounting system.

<div data-with-frame="true"><figure><img src="/files/yqGpy2F7ijeA2P5DjoDd" alt="Forward receipts rule" width="563"><figcaption></figcaption></figure></div>

| Component | Value                                       |
| --------- | ------------------------------------------- |
| Condition | **Added label name** is "Receipt"           |
| Action    | **Forward to** → <accounting@mycompany.com> |

## Webhook to CRM

**Rule type:** Incoming message

Push conversation data to your CRM or other systems.

| Component | Value                                                    |
| --------- | -------------------------------------------------------- |
| Condition | **From** is in contacts                                  |
| Action    | **Send webhook** → <https://crm.example.com/api/missive> |

The webhook payload includes conversation ID, message content, sender info, and any labels.

## AI-powered auto-categorization

**Rule type:** Incoming message

Let AI read incoming messages and apply the right label.

| Component | Value                                                                            |
| --------- | -------------------------------------------------------------------------------- |
| Condition | **Email account** is <support@mycompany.com>                                     |
| Action    | **Add labels with AI** → "Categorize: Billing, Technical, Sales, Feedback, Spam" |

Combine with routing rules: a second rule triggered by label changes can move categorized conversations to the right team.

***

Have a rule template to share? [Send it to us](mailto:info@missiveapp.com?subject=Missive%20Rule%20Proposal).


---

# 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://missiveapp.com/docs/advanced-features/rules/examples/automation.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.