Gmail

To connect Gmail, open the in-app Connections settings.

Gmail is one of the two email backends Dispatch supports (the other is Outlook Mail). Once connected, the agent operates against your live mailbox. Drafts land in your real drafts folder; sent mail goes out from your address; label changes show up in the Gmail client.

OAuth scopes

Dispatch requests the Gmail API scopes it needs and no more. The exact scope set may evolve as the product changes; the in-app connect screen always shows the current request before you authorize.

Read capabilities

• List recent messages and search across your mailbox.
• Read message bodies, headers, attachments metadata, and thread structure.
• Read labels and label assignments.
• Read drafts.

Write capabilities

All writes carry the external-write risk annotation and pass through the permission gate.

• Create drafts.
• Send messages (new threads, replies, forwards).
• Apply, remove, and create labels.
• Archive (move out of inbox).
• Mark read/unread.

Permanent deletion is not exposed. Archiving is reversible from the Gmail client.

What automations can use

The agent can build automations that read or write Gmail:

• Email received (EMAIL_RECEIVED): trigger on incoming messages matching a filter (sender, subject, label).
• Email sent (EMAIL_SENT): trigger on messages the user sends.
• Scheduled actions that touch Gmail (for example, "every morning, summarize unread mail"). Scheduled actions can apply or remove labels; there is no separate label-change trigger.

Limits and behavior

• Rate limits. Heavy patterns (broad searches, batch label operations) are subject to Gmail's API quotas.
• Multi-account. A user can connect multiple Gmail accounts; the agent disambiguates by address when it matters.
• Send is gated. Send tools carry an external-write risk annotation and route through the permission gate. The gate consults your policy on every send once the permissionAgent enforcement flag is on for your org; while the flag is off the gate emits telemetry and lets the send through. Set rules like "always ask before sending outside @acme.com" in /preferences/permissions.md.
• No client-side cache. Reads go to Gmail directly; the agent does not maintain a local mirror of your mailbox.

Related

• Inbox: the user-facing surface that uses Gmail.
• Permission gate: how sends and other writes are gated.
• Cookbook: Learn my style