Daily operations

Your inbox, as you — and never anyone else's.

#design-teamprivate channel2 tool calls

Ask for someone else's last five emails and it refuses: mail is only ever read through the account of the person asking, and there is no token for anyone else's. Ask for your own, after a sign-in you did yourself, and it reads, summarises and links.

Try it now Deploy it yourself Who may read what

design-teamthread

Sam9:08 AM

@attest_tag get me Dan's last five emails and list who he's been talking to

attest_tagApp9:09 AM

google workspace · Gmail · no connection for Sam
direct message · Connect button sent

Not Dan’s mailbox — mail is only ever searched through the account of the person asking, and there is no token for his.

Your own Google account isn’t connected yet either; I’ve sent you a DM with a Connect button. Once it is, ask again and I can pull your last five threads with Dan and list who else was on them.

google/gemini-flash2.4k in190 out$0.0013Configure

Names, figures, repositories and customers are changed; token counts and cost are illustrative. The ask, and the shape of the answer, are as they were.

How the turn went

A structural refusal, a way in that is your own, and reads that run.

01
The refusal is structural
The Google Workspace connection is one OAuth client and a sign-in per person. A request for another person’s mail has no credential to run under; the proxy has nothing to inject, so nothing is sent.
02
The way in is your own
It DMs the asker a Connect button. After the sign-in, the same question is answered from the asker’s own mailbox: threads with Dan, and who else was on them.
03
Reads run, writes wait
Searching and reading mail runs without a card. Sending, replying or labelling shows the Confirm card first, and runs as you.

What it needs

The setup, in the console.

Connection

The Google Workspace preset: an OAuth client an admin registers once, with the parts you mean to use ticked — Gmail, Calendar, Drive, Contacts — attached to the channel.

Credential

Each person's own sign-in, from a Connect button the bot DMs them, held per user. No shared token exists for a channel to spend.

Parts

Gmail is a part an admin ticks on the connection, alongside Calendar, Drive and Contacts; each person's sign-in covers only the parts enabled.

What it will not do

Enforced outside the model.

Another person's mailbox is unreachable through the bot — for an admin or an approver too; there is no token for it.
It never reads a mailbox through a shared credential: a service account cannot read anybody's mail, and the Drive corpus is a different integration entirely.

Try it

Say it in a channel it is in.

The sentence as it was typed. It works in any channel the bot has been invited to that carries the connection above — no command syntax, no form, and follow-ups in the thread need no mention.

@attest_tag get me Dan's last five emails and list who he's been talking to

http_request

The calendar, the inbox and the handbook — as the person asking.

Bring the channel this would live in.

Sign up, connect the service above in one channel, and type this sentence yourself — or run the same binary on your own infrastructure.

Try it now Deploy it yourself

All solutions