Bob with Gmail: turn an inbox into finished work

Matthew, founder of Bob · Published July 30, 2026

Short answer

Connect your Gmail account and Bob can search messages, read threads, inspect labels, create drafts, and send email while you stay in Slack. The connection is personal: Bob uses the access of the person who connected it, not a shared company super-account.

That makes Gmail most useful as part of a larger job. Bob can find the customer thread, check the related HubSpot deal, draft the reply, and ask before anything leaves your inbox.

What Bob can actually do in Gmail

Bob's purpose-built Gmail connection supports message search, thread reading, label listing, draft creation, and sending. Those actions map to Gmail's documented message and draft APIs, including Google's draft and sending flow.

Reads can move automatically. Creating a draft is reversible, while sending is an external write. Bob shows the proposed action and asks by default before the message is sent. Your team can grant a narrow standing policy later, but a broad permission is not required to get value from the connection.

Five useful Bob and Gmail workflows

1. Morning inbox brief

"Find unread messages from customers and partners since yesterday. Group them by urgency and tell me which need a reply today."

Bob can search and read the matching threads, then return the useful decisions in Slack instead of another list of subject lines.

2. Draft a reply with the full account context

"Read Acme's latest thread, check their HubSpot deal and our open Jira issue, then draft a concise update. Do not send it."

The result is a Gmail draft grounded in more than the inbox. You can edit it in Gmail or tell Bob what to change before approving a send.

3. Recover commitments from a long thread

"Read the launch thread with Northstar and list every commitment, owner, and date. Create Linear issues for our commitments after I approve."

Email becomes structured work, with the original thread preserved as source context.

4. Follow up on stale conversations

"Find sales threads where we promised a follow-up more than five business days ago. Draft the missing replies and show them to me."

This works best as a review queue. Bob finds the gap and prepares the work without silently emailing a customer.

5. Send an approved update

"Send the approved project update to the recipients on the launch thread."

Bob asks before the send unless you have deliberately granted that exact kind of action. The completed run records what he used, what he changed, and what it cost.

How the Gmail connection works

1. Ask Bob in Slack to connect Gmail.
2. Open the secure connection button and sign in with Google.
3. Review the requested OAuth access and choose the Google account Bob should use.
4. Return to Slack and retry the original request.

Each user connects their own Gmail account. Bob does not ask for a password or a token in Slack, and he cannot see mail outside the connected account's permissions.

Limits worth knowing

• Account scope is real. Bob sees what the connected person can see, not every mailbox in the domain.
• Search quality depends on the request. A sender, domain, label, or date range produces a more reliable result than "find that email."
• Sending has consequences. Keep the default approval gate until a repeatable workflow has earned narrower standing access.
• Email is not the whole record. Join Gmail with Calendar, HubSpot, Jira, Linear, or Drive when the answer depends on those systems.

FAQ

What can Bob do with Gmail?

Bob can search messages, read threads, list labels, create drafts, and send email through the Gmail connection.

Does Bob use my Gmail account or a shared company inbox?

Gmail is personal in Bob. Each person connects their own Google account, and Bob acts with that person's access.

Can Bob send email without asking?

Bob asks before external writes by default. A user can later grant a narrow standing policy for a trusted repeat workflow.

Can Bob read every email in the company?

No. Bob is limited to the connected Google account and the OAuth access that person granted.

Start with a draft, not an autonomous inbox

Ask Bob to produce one daily brief or one grounded draft. Check it against the source thread. Then connect Google Calendar, HubSpot, or Google Drive when the workflow needs more context.