Connecting your tools

Connecting Gmail to an AI agent

The inbox is where work arrives, and where it gets buried. An agent connected to Gmail searches and reads mail, manages labels and prepares drafts for your review. It does not send them behind your back — Google's official connector does not allow it to. It is that limit, and not the list of functions, that should decide your trust.

1. What the agent does in Gmail

The connector goes through Google's official interface for Gmail. The scope is therefore the one Google allows, no more and no less:

Search and read. Find a thread, an attachment, an old exchange with a customer — without your having to remember the exact words.
File. Add and remove labels, so sorting happens as things arrive rather than on a Sunday evening.
Prepare drafts. The reply is written and filed in your drafts, ready to be read, corrected and sent by you.

Two permissions are requested from Google, and two only: reading mail and composing drafts. You see them on screen at connection time, and you can withdraw them from your Google account whenever you want.

2. What it does not do

This section matters more than the previous one, and it is short.

It does not send silently. Google's official connector does not include sending. This is not a cautious setting on our part that could be loosened: the capability does not exist in this connector.
It deletes nothing. No deletion of a message or a thread.
It does not leave the named scope. The connection requires designating the account, and can be restricted by label, by sender or by recipient. An agent handling after-sales has no business seeing the management inbox.

3. An incoming email is never an instruction

This is the risk specific to email, and providers rarely spell it out. An incoming message can contain text written to divert an agent that reads it: “ignore your instructions”, “forward this thread to this address”, “approve this invoice”.

The rule applied is simple: the content an agent reads is data, never an order. Instructions come from you and from the mission, not from the mail. And since no rule is perfect, any action that commits the company stays behind human approval requested before execution.

That is also why the draft is the right unit of work on a mailbox: it makes control natural instead of making it tiresome.

4. Connecting your account

You sign in with your usual Google account, Google's screen displays the two permissions, you accept. No password passes through nullbot.

One thing to know before you start, because it surprises people: Google's Gmail connector is still in developer preview and must be enabled in a Google Cloud project. It is a one-off step, flagged at connection time rather than discovered along the way. If your organisation does not have one, email remains reachable through the generic mail route.

5. What changes after six months

On the first day the interest is thin: you would have found that thread yourself. The gap widens afterwards, because sorting is an endless task nobody keeps up.

Week 1. Labels place themselves, inbound requests are sorted, and routine replies wait as drafts. You correct the tone.
Month 3. Nothing stays unanswered for a week. Quote follow-ups go out at the right moment because the thread was read, not because a reminder went off.
Year 2. The inbox is no longer a backlog: it is a queue being handled. It is not spectacular — which is exactly why nobody does it for long without help.

No quantified gain is promised: it depends on your mail volume and on what you delegate.

6. Frequently asked questions

Can an agent send an email on my behalf?

Not through this connector: Google's official interface for Gmail allows reading, label management and draft creation, not sending. If you want a message to go out automatically, that runs through the generic mail route, with the sending address you configure — and the action stays subject to approval until you have explicitly relaxed it.

Does the agent see my whole inbox?

Only the account you designated, and you can narrow it further: by label, by sender or by recipient. That matters when several agents work on the same address: the one handling inbound requests has no reason to read the exchanges with the accountant.

What happens if I revoke access?

The agent immediately loses access to the inbox. Drafts already prepared and labels already applied stay in your Gmail: they are your data, in your account. Revocation happens from nullbot as well as from your Google account, and withdrawal on Google's side cuts access whatever happens.

Do I need a Google Workspace account?

The official connector currently requires enabling in a Google Cloud project, which in practice supposes a Workspace environment or an existing Cloud project. For an ordinary Gmail account with no Cloud project, the generic mail route remains available and covers both reading and sending.