Connecting Gmail lets agents send email as the authorized user and read the mailbox — useful for follow-ups, ticket replies, and email-triggered workflows.

​
Create Google OAuth credentials

1

Create a project

In the Google Cloud Console, create or select a project.
2

Enable the Gmail API

APIs & Services → Library → search “Gmail API” → Enable. The flow fails at call time, not consent time, if you skip this.
3

Configure the consent screen

Under OAuth consent screen, choose Internal if everyone using this connection is in your Google Workspace organization, or External otherwise. Add the scopes below.
4

Create the client

Credentials → Create Credentials → OAuth client ID → Web application. Add your redirect URI:

​
Configure GoConva

Google integrations share one client:
GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET are shared across Gmail, Google Sheets, Drive, and Slides — but each has its own redirect variable. Register every redirect URI you use on the same OAuth client.

​
Scopes requested

gmail.readonly grants read access to the entire mailbox. Google treats it as a restricted scope — an External app in production requires a security assessment before Google will lift the 100-user cap. Internal apps within a Workspace organization are exempt.

​
Connect

In your workspace, go to Settings → Integrations, find Gmail, and click Connect. Choose the Google account whose mailbox the agents should use. GoConva requests offline access, so Google issues a refresh token and the connection survives token expiry without you reconnecting.

​
Sending email

Add a Gmail step to a workflow and set the recipient, subject, and body. Mail is sent as the authorized account and appears in that account’s Sent folder, so replies come back to a real mailbox someone can read.

​
Troubleshooting