Messaging

AI agents that use Gmail

UtilitySpaces gives an AI agent scoped access to Gmail through its own encrypted connection, not your password. The agent can call 4 named Gmail tools, and the one that writes waits for a person's approval unless an admin has set the connection to run without asking. Every call is written to a hash-chained audit log with its arguments and its result.

What an agent can do in Gmail

Read, search, label, and send email from the connected Gmail inbox. An agent calls these by name, and matching is exact.

Every tool a Gmail connection exposes, and whether it writes, which waits for approval by default
Tool	What it does	Waits for approval by default
List labels	List the mailbox's labels.	No — read only
List messages	List/search messages in the inbox.	No — read only
Get message	Get a single message by id.	No — read only
Send message	Send an email (raw = base64url-encoded RFC 2822 message).	Yes — it writes

3 read tools, 1 write tool. Generated from the connector catalogue the product runs on, so it cannot list a tool that does not exist.

What teams hand an agent in Gmail

Teams hand an agent the inbox reading they do not have time for: searching with List messages, opening a thread with Get message, and turning it into a summary or a task. Send message is the only write, and it waits for a person to approve it unless an admin has set this connection to run without asking, so by default the agent drafts the reply and a person decides whether it goes.

Triage the mailbox each morning by searching unread messages, grouping them by label, and listing which ones need a reply.
Pull the full thread when someone in chat asks about an email, by reading the message and summarising it in place.
Send a drafted reply or a follow-up when a message has waited past an agreed number of days (after a person approves it)

Before you let it write, or keep out: Send message goes out under the connected person's name, so read each send before approving it, and think hard before letting it run without asking; the connector cannot recall a sent email or move one to drafts.

What waits for a person

Reads run on their own. These do not — each one waits in Approvals for an owner or admin unless an admin has set this connection to run writes without asking, and every call toGmail, approved, rejected or unattended, is logged.

Send message POST

What connecting Gmail takes

Gmail uses OAuth, so you authorise in Gmail’s own screen and no secret is ever typed into UtilitySpaces. The connection asks for 1 scope, fixed in the catalogue and shown to you by Gmail before you agree:

https://www.googleapis.com/auth/gmail.modify

Credentials are encrypted and bound to your workspace, never read back, and every outbound call passes one guarded fetch — the connector security posture sets out exactly how, and the security page covers the platform around it.

Where Gmail fits

Give an agent Gmail work by writing a message in the inbox, or put its tools in a scheduled flow. What the run cost is on the cost breakdown.

Other messaging integrations: Chatwoot, Discord, Microsoft Outlook. Or see every application agents can connect to.

See it doing your actual work

Open a demo workspace, connect one app, and give an agent a real job. No card, no sales call.

Try the demo See pricing

We reply to every message within one business day.