Niches · Mailbox access

React to new mail as it arrives

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

0companies, full fit
8companies, fit with a limit
8companies carry the tag
14share of the category's work
5first-hand accounts

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. No docs we read state these figures, so they don't count against a listing here.

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 8

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.

ListingWhy
Aurinko Email API F
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. source
email-agent-mcp B
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. source
EmailEngine BB
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. source
Fastmail API (JMAP) C
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. source
Gmail API A
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. source
Nylas Email API A
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. source
Outlook Mail (Microsoft Graph) C
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. source
Unipile B
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. source

Couldn't check 1

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

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

Doesn't do this job 2

Listings in the category that do something else, with the reason.

ListingWhy
Himalaya C
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. source
Zoho Mail API D
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. source

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)

The same as data: /api/v1/use-cases/mailbox-access.watch-new-mail.json, or the MCP tool get_use_case with id mailbox-access.watch-new-mail. Other jobs in this category: /api/v1/niches?category=mailbox-access.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.