# Rules FAQ

<details>

<summary>How do I replicate "Move to label" with a rule?</summary>

Labeling and archiving are two separate things in Missive. When you manually use **Move to label**, you're doing two things at once: applying the label and archiving the conversation from your inbox.

Rules don't have a "Move to" action - they have separate **Add label(s)** and **Archive** actions. To replicate the manual **Move to label** behavior, add both actions to your rule:

1. **Add label(s)** - applies the label
2. **Archive (from Team Inbox)** and/or **Archive** - removes it from the inbox

Using only **Add label(s)** will apply the label but leave the conversation in the inbox.

</details>

<details>

<summary>Why are time-based conditions greyed out?</summary>

**Delay** and the **Unreplied/Unassigned and open after** conditions are mutually exclusive - a rule can only use one type.

If your rule already has a **Delay** condition, the **Unreplied and open after** and **Unassigned and open after** options will be greyed out, and vice versa.

To switch to a different type, remove the existing time-based condition first.

See [How Delay differs from Unreplied/Unassigned and open after](/docs/advanced-features/rules/conditions.md#how-delay-differs-from-unreplied-unassigned-and-open-after) for an explanation of how each works.

</details>

<details>

<summary>An error says my rule will never match; what can I do?</summary>

If you see this error when saving your rule…

<figure><img src="/files/ttCEcXepObQwuKeJvwK5" alt="An example of an impossible combinaison of rule conditions."><figcaption></figcaption></figure>

…it means the conditions will never match any message.

In the image above, it fails because an email can't come from more than one **From** address, and the rule expects **All** conditions to match.

To fix this, nest one of the **From** conditions in a new block by pressing the > arrow:

<figure><img src="/files/LYQwA53MtkUDmhXAMvrM" alt="Nest a condition block."><figcaption></figcaption></figure>

In the new block, switch from *All* to *At least one* condition matched:

<figure><img src="/files/exK4gSdUWAIskmrKNaMZ" alt="A nice rule!"><figcaption></figcaption></figure>

See [Complex rules](/docs/advanced-features/rules/examples/complex-rules.md) for more on combining conditions.

</details>

<details>

<summary>How do I copy a rule from personal to organization (or vice versa)?</summary>

Click **•••** on any rule and select **Export**. Then click the **Import** button in the bottom-right corner of the rule editor (when creating a new rule).

This works in both directions - you can export a personal rule and import it as an organization rule, or export an organization rule and import it as a personal rule. You can also use this to duplicate a rule across multiple organizations if you belong to more than one.

</details>

<details>

<summary>Can I run a rule on existing emails?</summary>

No. Rules only run on new incoming messages, outgoing messages, or user actions going forward - they can't be applied retroactively to conversations that already exist.

Once your rule is set up, it handles new emails automatically.

</details>

<details>

<summary>Why is my rule not working?</summary>

Most common cause: you created a personal rule when you needed an organization rule (or vice versa).

**Personal rules** only trigger on private conversations.

**Organization rules** only trigger on conversations shared with your organization.

If the conversation has a colored banner, it's shared with your organization - you need an organization rule.

<figure><img src="/files/R3QQGz99Sl7Kqb2YMGC4" alt="" width="411.5"><figcaption></figcaption></figure>

</details>

<details>

<summary>Why doesn't my rule trigger on spam emails?</summary>

Rules don't run on emails that land in the spam folder unless you explicitly check for spam.

To apply rules to spam emails, add a **Message properties - Spam?** condition to your rule.

Without this condition, Missive skips rule processing for spam to prevent unwanted automation on junk mail.

</details>

<details>

<summary>How can I see which rules ran on a conversation?</summary>

Hover over the word **Rule** on the conversation event to see the rule name.

<figure><img src="/files/KXrAEX4LuKcD6aFy644w" alt="View the rule that was triggered by hovering over with your mouse" width="470"><figcaption></figcaption></figure>

If you're an admin or it's your personal rule, click **Edit** to modify it.

</details>

<details>

<summary>Can I see when a rule triggers a webhook?</summary>

Yes. Go to **Settings** > **Preferences** > **Appearance** and enable **Show rule webhook events**.

Once enabled, a "\[rule name] triggered a webhook" event appears in conversation view each time a rule fires a webhook action.

This setting is off by default.

</details>

<details>

<summary>Can I hide rule events in conversations?</summary>

Go to **Settings** > **Preferences** > **Appearance** and disable conversation events.

<figure><img src="/files/Mpl73MFtzRWVo8NxomwH" alt="" width="942"><figcaption></figcaption></figure>

To show events in a specific conversation, select **Show events** from the conversation menu:

<figure><img src="/files/BRV6D16YbHMJzrcLtMUM" alt="" width="207"><figcaption></figcaption></figure>

</details>

<details>

<summary>How do I target replies vs new messages?</summary>

Two ways:

**Check the message count:**

<figure><img src="/files/JQi1J9wFuKbeoM8xOYyi" alt="" width="706"><figcaption></figcaption></figure>

**Check for "Re:" in the subject:**

<figure><img src="/files/82TLbS4XhUelXfzHgxfb" alt="" width="704"><figcaption></figcaption></figure>

Add more conditions for other languages (Re:, AW:, SV:, etc.).

</details>

<details>

<summary>What is the limit on rules I can create?</summary>

The maximum number of rules you can create is **1,000 personal rules** and **1,000 organization rules** per organization.

</details>

<details>

<summary>Can I try rules on the Starter plan?</summary>

Rules require Productive or Business. Starter users can trial rules for 30 days.

</details>

<details>

<summary>Can I auto follow-up on emails I send?</summary>

Yes - create an outgoing email rule with a delay condition and a "Send response" action.

{% embed url="<https://youtu.be/KLLonSHhA2w>" %}

</details>

<details>

<summary>Can I detect high importance emails from Outlook users?</summary>

Yes. Outlook users can mark outgoing emails as "High Importance" using RFC 4021 headers. While Missive doesn't support sending these flags, you can detect them in incoming emails using the **Headers** condition.

Create an incoming email rule with a **Headers** condition and check for either:

* `Importance: high` (standard header)
* `X-Priority: 1` (alternative header)

Then apply actions like adding a label, assigning to someone, or sending a notification.

**Note:** Gmail doesn't support high importance flags. This only works with emails sent from Outlook or other clients that support RFC 4021 priority headers.

</details>

<details>

<summary>Why did my incoming email rule trigger multiple times?</summary>

Incoming email rules trigger **once per email account** that receives the message.

When multiple accounts receive the same message (via CC, BCC, or email forwarding), the rule runs separately for each account.

**Actions that produce the same result each time:**

* Adding labels
* Assigning users
* Closing conversations

**Actions that produce different results each time:**

* **Forward** - Sends multiple forwarded messages

**To run the rule only once:**

Add an **Email account** condition to limit the rule to one specific account. This ensures the rule triggers once, regardless of how many accounts receive the message.

</details>

<details>

<summary>Can I chain rules together (use one rule to trigger another)?</summary>

No. User action rules only trigger when actual users perform those actions, not when rules perform them.

For example:

* An incoming message rule adds a label → **Does not trigger** a "Label change" user action rule
* An outgoing message rule assigns a user → **Does not trigger** an "Assignee changed" user action rule
* A rule closes a conversation → **Does not trigger** a "Conversation closed" user action rule

Put all your actions in a single rule instead of trying to chain multiple rules together.

</details>

<details>

<summary>Why doesn't my personal rule with a mention condition trigger?</summary>

The **Mention** condition on "New comment" rules only works with organization rules, not personal rules.

When you're mentioned in a conversation, it automatically becomes shared with your organization. Personal conversations don't have mentions because mentions only exist in shared conversations.

To use the **Mention** condition, create an organization rule instead.

</details>


---

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