# React to new mail as it arrives

> React to new mail as it arrives: 0 companies fully do it, 8 with a limit, 8 carry the tag. Every listing in Mailbox access with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/mailbox-access.watch-new-mail/
- Markdown: https://www.anchorterminal.com/niches/mailbox-access.watch-new-mail/index.md (~1,300 tokens)
- Slim: https://www.anchorterminal.com/niches/mailbox-access.watch-new-mail/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/mailbox-access.watch-new-mail/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 8 | 8 | 14 | 5 |

## What counts as done

Every new message, Inbox and Sent, produces precisely one event or delta entry, and a restart resumes from the stored token without gaps or duplicates.

Measured, for our own tests: each event arrives within 60 seconds.

How agents ask for it: tell me when a work order comes in; log every new support email; keep our copy of the mailbox in sync

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Aurinko Email API (Yoxel, Inc.)**: sync/updated and sync/deleted page with nextDeltaToken so a restart resumes from a stored token, and webhook subscriptions exist on /email/messages, but sync must be restarted until ready and no latency or replay is documented.
- **email-agent-mcp (UseJunior)**: A separate watcher polls the mailbox and sends wake signals to OpenClaw, with recent fixes against notification loss across polling and checkpoints, but it is a poller with no stated interval or event per message, and targets one runtime.
- **EmailEngine (Postal Systems OÜ, Narva mnt 5, 10117 Tallinn, Estonia, registry code 14971894)**: messageNew webhooks fire for synced folders, including Sent, and carry X-EE-Wh-Event-Id for deduplication, but delivery is at-least-once, events are dropped after the last retry with only the last 500 failures kept for 7 days, and no latency is stated.
- **Fastmail API (JMAP) (Fastmail Pty Ltd, ACN 142 646 580, PO Box 234, Collins Street West, VIC 8007, Australia)**: Email/changes resumes from a stored state string and returns cannotCalculateChanges when it is too old, so restarts don't miss mail, but the developer page documents no push or webhook for new mail and no latency, so the agent polls.
- **Gmail API (Google LLC)**: watch pushes historyId changes through Pub/Sub and history.list resumes from a stored historyId, with a 404 when it is too old, but watch must be renewed every 7 days and no delivery latency is stated.
- **Nylas Email API (Nylas, Inc.)**: message.created webhooks push new mail, with .truncated variants to re-query, but acc-29 found new mail sometimes arriving as message.updated, acc-30 found older IMAP grants stopped sending message.created, and acc-33 found Sent not syncing on IMAP.
- **Outlook Mail (Microsoft Graph) (Microsoft Corporation)**: Change notifications retry for up to 4 hours and delta links resume per folder, but delta is a per-folder operation so Inbox and Sent need separate tokens, subscriptions and their validation tokens must be renewed, and no arrival latency is stated.
- **Unipile (UNIPILE SAS)**: The new-email webhook fires mail_received, mail_sent and mail_moved, covering Inbox and Sent, but the page documents no retry, replay or change token, so a restart can't resume without gaps.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **CloudPost (CloudPost (James Brooks))**: No docs; nothing on the site mentions events, webhooks or a change token.

- not this job: Himalaya (No legal entity found. Copyright Clément DOUIN (soywod)): The README documents no watch, IDLE, event or change-token command; each invocation opens a fresh session and the agent must poll envelope list.
- not this job: Zoho Mail API (Zoho Corporation Private Limited): The API index lists no webhook, push or change-token endpoint for mail; the agent can only poll search with a receivedTime.

## What stops agents finishing

- created events sometimes delivered as updated ones
- webhooks stopping for older IMAP connections
- Gmail watch expiring after 7 days without renewal

## Around it

Before: mailbox-access.connect-mailboxes. After: support.create-ticket, scheduling.create-event, crm.log-activity.

## Where this comes from

Weight 14 of 100 in Mailbox access: 5 of 36 counted mentions (acc-11, 29, 30, 32, 33)

As data: https://www.anchorterminal.com/api/v1/use-cases/mailbox-access.watch-new-mail.json, or the MCP tool get_use_case with id mailbox-access.watch-new-mail. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
