This page contains the setup guide and reference information for the Gmail connector.
Prerequisites
Before connecting your Gmail account, ensure that:
-
You have access to a Google Cloud Platform account.
Setup Guide
Follow these steps to set up OAuth credentials for Gmail and connect your account to Keragon:
-
Go to console.cloud.google.com.
-
Click Create Project and enter a name, such as "Keragon Gmail Project".
-
Click Create, then Select Project once it's created.
-
Open the menu icon and go to Enabled APIs & Services.
-
Use the Search field to find and select Gmail API.
-
Click Enable to activate the Gmail API.
-
Go back to the dashboard and click OAuth consent screen.
-
Choose Internal for User Type and click Create.
-
Fill in the following:
-
App name (e.g., "Keragon Gmail App")
-
User support email
-
Developer contact email
-
-
Click Save and continue.
-
On the Scopes page, click Add or remove scopes, search for Gmail API, select all necessary scopes, then click Update and Save and continue.
-
Return to the main dashboard and go to Credentials.
-
Click Create credentials > OAuth client ID.
-
For Application type, choose Web application.
-
Add the following URIs under Authorized redirect URIs:
-
https://api.us-east-1.keragon.com/rest/auth/callback
-
https://api.us-1.keragon.com/rest/auth/callback
-
-
Click Create.
-
Copy the Client ID and Client Secret.
-
Go to app.keragon.com and open the Gmail connector setup.
-
Paste the Client ID and Client Secret into the respective fields.
-
Click Connect to complete the integration.
Need more help connecting?
Check the fully extended Gmail connector setup guide for screenshots, detailed steps, and additional context.
Once set up, Keragon can authenticate and securely interact with your Gmail account using OAuth 2.0.
Troubleshooting and Common Errors
Error Message | Cause | Suggested Fix |
---|---|---|
redirect_uri_mismatch |
Redirect URIs not configured correctly in Google Cloud | Ensure both Keragon URIs are added exactly to the OAuth client settings. |
invalid_client |
Client ID or Secret is incorrect | Confirm you copied them from the correct credentials page. |
access_denied |
User denied access or consent screen issue | Retry the OAuth flow and approve all requested permissions. |
403 Forbidden |
Missing required Gmail API scopes | Recheck and update the scopes in the OAuth consent screen. |
Limitations and Notes
-
Authentication is handled using OAuth 2.0 with a custom Google Cloud application.
-
Both redirect URIs must be added during credential setup to ensure successful authentication.
-
Only Gmail accounts with proper permissions and API access can be used.