Docs/ Rules, context & knowledge

Inbox rules

Filters that fire on arrival — by keyword or by AI-understood concept.

Inbox rules run automatically on every sync, top-to-bottom by priority, so your inbox is already organised before you open the app.

How rules work

A rule is a match mode plus a set of conditions and a set of actions. The match mode decides how the conditions combine: ALL means every condition must be true (AND), ANY means one is enough (OR). When a message matches, the rule's actions run immediately.

Rules run automatically on every sync, evaluated top-to-bottom in the priority order you set. You can also re-run your rules on demand — handy after you add or edit a rule and want to apply it to mail that's already in your inbox.

Priority order matters

Rules fire top-to-bottom by priority. A rule can end with the Stop action, which halts processing so no lower-priority rule touches that message — put specific overrides high and broad catch-alls low.

Match conditions

Add as many conditions as you need and choose a match mode (ALL = AND, ANY = OR). Each condition tests a field with an operator. Available operators are: contains, equals, starts with, ends with, in (any of a list), not in, and AI match — a semantic operator that judges the field by meaning (it costs credits).

Condition fieldWhat it matches on
FromThe sender's email address
From domainThe sender's domain (e.g. github.com)
ToA recipient address on the message
SubjectThe subject line
BodyThe message body text
Has attachmentWhether the message carries an attachment
List mailBulk / mailing-list mail (List-Unsubscribe present)
AI tagThe agent's classification: vip, reply-today, fyi, newsletter, receipt, calendar, or cold
Client profileThe client profile the message is associated with
AccountWhich connected mailbox received it
Is unreadWhether the message is still unread
Is importantWhether the message is marked important

AI match reads meaning, not keywords

Most operators are literal (contains, equals, in…). The AI match operator asks the model to judge a field by meaning — catching paraphrases and indirect phrasing a keyword test would miss. It consumes credits per message, so reserve it for conditions plain matching can't express.

Building a rule

Every rule is assembled the same way. Work through these steps in the rule editor:

  1. 1

    Choose the match mode

    Pick ALL (every condition must be true — AND) or ANY (any single condition is enough — OR). This decides how the conditions below combine.

  2. 2

    Add conditions

    Add one or more conditions. For each, pick a field (from, subject, AI tag, list mail, account, is unread…) and an operator (contains, equals, starts with, ends with, in, not in, or AI match), then enter the value to test against.

  3. 3

    Add actions

    Choose what happens when the rule matches — move to a tab or folder, add a label or AI tag, archive, mute, snooze, route to the agent, and so on. A rule can carry several actions at once.

  4. 4

    Order it by priority

    Drag the rule into place in the list. Rules run top-to-bottom, so higher rules act first. Add a Stop action to a rule when you don't want lower rules to touch a message it matched.

Example rule — archive newsletters, tag them
Match modeANY (OR)
ConditionList mail = true
ConditionAI tag in [newsletter]
─────────────────────────────────
ActionMove to tab: newsletters
ActionAdd label: Reading
ActionMark read

Available actions

A rule can apply one or more of these 17 actions to a matched message:

ActionWhat it does
Move to tabSend to a tab: primary, important, vips, team, newsletters, receipts, or all
Move to folderFile into a folder: primary, social, promotions, or updates
Add labelAttach a label to the message
Add AI tagApply an AI tag (vip, reply-today, fyi, newsletter, receipt, calendar, cold)
Mark readClear the unread state
StarStar the message
ArchiveRemove from inbox without deleting
MuteSilence future replies on the thread
Move to spamRoute to the spam folder
Mark importantFlag as important
Unmark importantRemove the important flag
Snooze untilHide the message until a date you set
Assign client profileAssociate the message with a client profile
Route to agentHand the message to Copilot / Autopilot to draft or send
Notify meSend you a notification
StopStop processing — no further rules run on this message

Route to agent and stop

Two actions deserve special mention. Route to agent is the bridge between rules and the AI: instead of only filing a message, the rule hands it to the agent to draft — or, under Autopilot, send — a reply. This lets a deterministic rule decide which messages are worth the agent's attention, and the agent takes it from there under whatever approval mode you've set.

Stop ends rule processing for that message. Because rules run top-to-bottom by priority, a Stop on a high-priority rule prevents every lower rule from also acting — the clean way to make a specific rule an exception to your broader catch-alls.

Rules connect to the agent through Route to agent

Route to agent is how a rule and the AI agent work together: the rule handles matching and filing, then passes the message to Copilot or Autopilot to draft or send the reply.

Scope and running rules

Each rule can apply to all your mailboxes or only to specific ones — use the account scope (or an Account condition) to keep a rule tied to one inbox.

Rules run automatically on every sync. When you add or change a rule, run your rules on demand to apply them to mail that's already in the inbox instead of waiting for the next sync.

Frequently asked

Feature overview

Rules & Brain

Ready to try it?

Start Free Trial