Skip to main content
This older direct Google connection is unavailable while daoco’s Google verification is pending. Use Gmail through Composio, available now under Mail & Calendar with no preview opt-in. The restriction on this older connection does not apply to Composio.
Gmail Individual is a Dev Testing integration. Use it when one signed-in Google user should grant daoco access only to Gmail data available to that user during provider approval or testing. Google hosts the MCP endpoint for this connection. The steps below are a reference for the older connection. Enabling Dev Testing does not lift its verification restriction.

​
Connect Gmail Individual

1

Enable Dev Testing

A workspace owner or admin must enable Dev Testing integrations in Settings -> Preview features.
2

Open the Gmail Individual card

Open Connections -> Integrations -> Dev Testing and choose Gmail Individual.
3

Approve Google OAuth

Choose Connect, sign in with the Google user, and approve Gmail read and compose scopes.
4

Verify safely

Confirm the row is healthy, then run a minimal read-only /integration proof such as listing labels. Do not prove access by reading message bodies, subjects, snippets, or recipients.

​
What the connection can do

Read work (search threads, read a message, list labels) runs as soon as you ask. To write an email, the assistant drafts it in daoco: the approval card in chat shows the recipients, subject, and message, you can edit it there, and it sends (a new message or a reply) only after you approve that exact send. This connection does not create or read Gmail drafts, and it does not offer label, trash, or spam changes.

​
Workspace restrictions

If the Google account belongs to a restricted Workspace, a Google Workspace admin may need to trust the daoco OAuth app or allow these scopes:
daoco Google OAuth client ID:
This guide remains available for testing, but Gmail Individual is not part of the normal Mail & Calendar production category.