Routing and destinations

Routes and matching

Choose which source messages enter each mailbox, and which mailbox arrivals set off a trigger.

When to use it

Give each mailbox the routes it needs. Reuse one source across mailboxes with different conditions, and add triggers with their own conditions.

Example

The billing email account feeds Invoices when the subject contains invoice, and feeds Support with no condition. One invoice email lands in both mailboxes as the same canonical message.

Set it up

  1. In Mailboxes, select a mailbox and open Configure > Routes. Add a route and choose its source. Configure routes.
  2. Add source-relative conditions such as subject, order.status, or text. All must match. Empty conditions admit everything the source stores.
  3. If a condition needs uncaptured content, review and approve that source's capture first. Capture applies to every mailbox the source feeds.
  4. For push notices, add an Inbox trigger for a tested destination. Its rule uses event data paths such as subject, text, or fields.kind. Its match checks trusted source and optional internal author identity separately. Polling needs no trigger.
  5. Send a fresh captured message that matches and a nonmatching control. Check Mail and, if you use a trigger, the intended destination's handoff separately.

Important limits

  • A route selects mailbox membership, not reader access or notification delivery. Several matching routes into one mailbox create one membership.
  • Matching is case-sensitive for every source family. Operators include equals, not_equals, contains, not_contains, in, not_in, starts_with, not_starts_with, within_last_seconds, and not_within_last_seconds. Missing fields fail conditions, including negative conditions.
  • A route can inspect only stored fields. Adding routes never widens capture. Trigger rules must also use fields available from that mailbox's configured sources or permitted internal sends.
  • Trusted match.source accepts any, email, webhook, mcp, teams, slack, or internal. Only internal accepts authorAgentId. The internal predicate verifies the service-managed source and authenticated author, not payload claims or display names.
  • Only matching Inbox arrivals from new acceptance create notices. Read state, organization, grants, and silent backfill do not create notices. Sent has no triggers.
  • Route and trigger edits apply to later acceptance. They do not rewrite history or recall requests already in flight.

Troubleshooting

  • If a route is refused, check that the source stores every field in its conditions.
  • If unrelated events enter, inspect the conditions on each route into that mailbox. A condition on one route does not filter another.
Open Agent Doorbell