How to register a Google developer app and get OAuth 2 credentials
May 29, 2025
- Create a Google Cloud Platform project:
- Go to the Google Cloud Console (https://console.cloud.google.com/) and sign in.
- If you don't have a project, click the "Select a project" dropdown and choose "New Project".
- Give your project a name and click "Create".
- Enable the Necessary APIs
- In the Google Cloud Console, make sure your newly created or existing project is selected.
- Navigate to APIs & Services > Library
- Search for the specific API you want to use (e.g., "Gmail API", "Google Drive API", "Google Calendar API").
- For Google Directory, make sure that you have the Admin SDK API enabled.
- Click on the API from the search results.
- Click the "Enable" button. Repeat this for all Google APIs your application will need to access
- Configure the OAuth Consent Screen
- In the Google Cloud Console, go to Google Auth Platform
- Fill in what is asked and click Create
- Click "Create"
- Go to Auth Branding and fill in the required Information
- Scopes: Select the scopes your application needs. Scopes define the permissions your app is requesting (e.g., read emails, access calendar). Be specific and only request the scopes you absolutely need.
- Go to Auth Data Access
- You will at least need
openid
,userinfo.email
,userinfo.profile
,admin.directory.group.readonly
andadmin.directory.user
oradmin.directory.user.readonly
. - The scopes needed by other Google integrations can be found in the Unified App, for example:
- Review the information and click "Save and Continue" through the steps. If you selected "External" and are just testing, you can often leave your app in "Testing" publishing status. If you intend for it to be publicly available, you'll eventually need to "Publish" it and potentially go through verification.
- Create OAuth 2.0 Credentials
- Go to Auth Clients in the Google Cloud Console.
- Click on "+ Create Client" at the top of the page, Follow the steps
- Configure the authorized redirect URIs. Get the correct value from the Integration, for example Google Drive
- Copy your Client ID and Secret
- Enter these values in your Integrations, for example:
- Publish your Application
- Go to Auth Audience
- Click on Publish app
- Once your application is approved and verified it will start showing your application name on the authorization consent screen. Until then it will be showing the "unified.to" name, which is inferred from the redirect URL.
Are we missing anything? Let us know