Mail — Gmail
Reads recent mail, including your sent items, because that is where your own promises are. A cheap filter drops the newsletters and the no-reply senders before a model reads anything, then what survives becomes a capture you approve.
Read wide. Write narrow.
The commitments that go missing are not in the notes you remembered to take — they are in the mail you skimmed on a Tuesday and the message that ended in “sure, I'll sort that”. Zephyr connects to where they actually live. Reading is all a connection does on its own; a reply or a calendar change goes out only with its own permission and your approval of that exact change.
What connects today
Three connectors, one rule
Each one reads broadly enough to find a commitment, and connecting one sends nothing to anyone. Gmail and Google Calendar connect read-only; sending a reply or changing your calendar is a separate permission you turn on per account, and even then each one waits for your approval. That is enforced by the scopes Zephyr holds, not by a promise about how it behaves.
Calendar — Google
Reads events and who is on them, so the person brief can arrive before a meeting rather than waiting to be asked for. It does not read event descriptions — those hold dial-in codes and interview notes. A private focus hold, moving a meeting you organise or asking another organiser to move one happens only after you allow calendar changes for that account and approve that exact change.
Slack — on demand
A Send to Zephyr action on any message. Zephyr sees what you hand it and nothing else: no channel history, no DMs, no bot sitting in the workspace reading along.
60%
of a knowledge worker's time goes on coordination — searching,
chasing, retyping — rather than the work they were hired for.
Most of that coordination arrives through a mailbox.
Asana, Anatomy of Work Index 2021, 13,123 knowledge workers
The rules every connector inherits
Six constraints, none of them negotiable
Read wide, write narrow
A connector may read broadly to find commitments. Anything it would write — a reply, a calendar change — is prepared for a person and happens only once they approve it.
No autonomous messages
Zephyr never sends a mail, a message or an invite on its own. A reply goes out only after you have allowed sending for that Gmail account and approved the exact message and its recipients, and it is marked sent only when Gmail confirms it. Without that permission, Zephyr drafts and you send from your own mail app. Auto-send is not on the roadmap at any price.
Content is data, never instructions
A mail saying “ignore your previous instructions” is a mail with a strange sentence in it. Every payload goes through the same fencing a capture does.
Tokens never touch the phone
Refresh tokens live server-side, encrypted, reachable only by the function that uses them. The app holds a connection status, never a credential.
Least scope that works
Read-only where read-only will do. Connecting asks for gmail.readonly and calendar.readonly; gmail.send and calendar.events are asked for separately, per account, only when you turn on sending or calendar changes. A test fails the build if the reading grant ever asks for more.
Revocable and legible
One screen lists what is connected, what it last read, and a disconnect that revokes upstream rather than only forgetting locally.
Reading a mailbox
An inbox is thousands of messages. Most of them are nothing.
Handing every message to a model would be a bill with no floor, so a deterministic filter runs first and costs nothing: bulk headers, no-reply senders and mail with no commitment language in it are dropped before anything expensive happens.
The bias is deliberately towards reading. A false skip is a commitment Zephyr never saw, which is the one failure the product cannot afford — so the filter rejects things that are structurally not correspondence rather than trying to judge what a sentence means. Judging meaning is the model's job.
Mail also cannot run up a bill on its own. It reads new mail only while you have credits left, and each run reads a bounded number of messages, so a run never fetches mail that nothing could act on.
MAIL · WHAT WAS READ
412 messages seen · 39 worth reading · 6 became actions
Bulk sender, list header
288
No commitment language
85
“I'll get you that by Friday”
6
Being straight about it
What is not connected yet
A connector exists when something reads from it. Until then the row in Settings says “Soon” rather than offering a button that opens a consent screen and lands nowhere.
Outlook
Outlook mail and calendar are not available. The row says “Soon” until Zephyr can read them end to end; Gmail and Google Calendar are what read today.
WhatsApp and Messages
Not connected and not offered. Neither gives Zephyr an approved way to read along, so neither appears as a button.
Watching a channel
Slack's message action is deliberate and small. Continuously ingesting selected channels is higher value, far higher noise, and a separate opt-in decision.
Jira, Asana, Linear
Two-way sync with the tool your team runs on is a real ask, and the hard part is the mapping, not the API. It needs a per-connection mapping screen first.
Teams
The same shape as Slack, and it follows Slack rather than arriving with it.
Zapier
One webhook in, one out, for the long tail of everything else. Not built.
Ready to see it on your own work?
Zephyr is in development for iOS, Android and the web. Join the early access list.