{/* Generated by scripts/generate-integration-catalog.mjs. Do not edit by hand. */}
At a glance
- Availability: Enabled by default.
- Authentication: OAuth 2.0.
- Connection: A user authorizes the connection in the provider's consent screen.
- Scopes:
https://www.googleapis.com/auth/gmail.modify.
Credentials
Set these per environment. See Connect an integration.
These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.
Setup
- Choose who owns the Google OAuth app: On hosted Veryfront, Gmail uses the Veryfront-managed Google OAuth app: connect Gmail from the project's integrations and approve the Google consent screen, no environment variables needed. Set GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET only to use your own Google OAuth app, which is required for local and self-hosted runs.
- Enable the Gmail API: In the Google Cloud project that owns your OAuth app, enable the Gmail API.
- Configure the OAuth consent screen: Configure the consent screen and add the scopes this connector requests. While the app's publishing status is Testing, only the test users you list can authorize it, and Google expires their refresh tokens after 7 days, so they must reconnect weekly. Publishing an app that requests Gmail's restricted scopes to external users requires Google's OAuth app verification.
- Create an OAuth client: Create an OAuth client ID of type Web application. Add the redirect URI of the environment that completes the flow: https://api.veryfront.com/oauth/callback/gmail for hosted Veryfront, or your app origin followed by /api/auth/gmail/callback for a local or self-hosted app. Set GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET from the client.
- Verify access: Run List Emails (read-only). It returns message summaries for the connected mailbox without changing it.
Provider notes
- The connection requests gmail.modify for reading, drafts, sending, labels, and reversible Trash. Permanent message and thread deletion is not exposed.
- Every list, get and search tool is read-only. Tools that send, draft, label, archive, trash or delete mail are marked as writes and need write authority.
- Each Gmail connection belongs to the Google account that approved consent; the tools act on that mailbox only.
Tools
Verify the connection
Call a read tool such as gmail__list_emails with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.