This page contains the setup guide and reference information for the Google Drive connector.
Prerequisites
Before connecting your Google Drive account, ensure that:
-
You have access to a Google Cloud Platform account.
Setup Guide
Follow these steps to create OAuth credentials and connect Google Drive to Keragon:
-
Visit console.cloud.google.com and sign in.
-
Click Create Project and provide a project name (e.g., "Keragon Google Drive Project"), then click Save.
-
Click Select Project to activate the newly created project.
-
In the sidebar, go to API & Services > OAuth consent screen.
-
Choose Internal as the user type and click Create.
-
Fill in:
-
App name
-
User support email
-
Developer contact information
-
-
Click Save and continue.
-
Go to Enabled APIs & Services, then click Enable APIs and Services.
-
Search for and select Google Drive API, then click Enable.
-
Navigate to Credentials in the sidebar.
-
Click Create Credentials > OAuth client ID.
-
Choose Web application as the application type.
-
Enter a name (e.g., "Keragon").
-
Under Authorized redirect URIs, add:
-
https://api.us-1.keragon.com/rest/auth/callback
-
https://api.us-east-1.keragon.com/rest/auth/callback
-
-
Click Create to generate your credentials.
-
Copy the Client ID and Client Secret.
-
Go to app.keragon.com, open the Google Drive connector setup.
-
Paste the Client ID and Client Secret into their respective fields.
-
Click Connect to authorize and complete the integration.
Need more help connecting?
Check the fully extended Google Drive connector setup guide for screenshots, detailed steps, and additional context.
Note: Ensure both Keragon redirect URIs are added correctly to avoid redirect errors during authentication.
Troubleshooting and Common Errors
Error Message | Cause | Suggested Fix |
---|---|---|
redirect_uri_mismatch |
Incorrect or missing redirect URI in Google Cloud setup | Ensure both Keragon URIs are added exactly in your OAuth client configuration. |
invalid_client |
Incorrect Client ID or Client Secret | Double-check that the values are copied accurately from Google Cloud. |
access_denied |
User declined permission during OAuth flow | Retry the authorization and accept the requested permissions. |
403 Forbidden |
Missing Google Drive API access or wrong OAuth scope | Ensure the Drive API is enabled and correct scopes are selected. |
Limitations and Notes
-
The Google Drive connector uses OAuth 2.0 for secure access.
-
Both redirect URIs must be set exactly as shown in your Google Cloud project for successful authentication.