Google Chat

Access the Google Chat API in 2 minutes 💨

🚀 Quickstart

1. Create an integration

   In Nango (free signup), go to Integrations -> Configure New Integration -> Google Chat. Nango doesn’t provide a test OAuth app for Google Chat yet. You’ll need to set up your own by following these instructions. After that, make sure to add the OAuth client ID, secret, and scopes in the integration settings in Nango.

   Nango has credentials you can use for testing. Activate them in the dashboard.

2. Authorize Google Chat

   Go to Connections -> Add Test Connection -> Authorize, then log in to Google Chat. Later, you’ll let your users do the same directly from your app.

3. Call the Google Chat API

   Let’s make your first request to the Google Chat API (fetch a list of spaces). Replace the placeholders below with your secret key, integration ID, and connection ID:

   cURL

   curl "https://api.nango.dev/proxy/v1/spaces?pageSize=10" \
     -H "Authorization: Bearer <NANGO-SECRET-KEY>" \
     -H "Provider-Config-Key: <INTEGRATION-ID>" \
     -H "Connection-Id: <CONNECTION-ID>"
   

   Node

   Install Nango’s backend SDK with npm i @nangohq/node. Then run:

   import { Nango } from '@nangohq/node';
   
   const nango = new Nango({ secretKey: '<NANGO-SECRET-KEY>' });
   
   const res = await nango.get({
       endpoint: '/v1/spaces',
       params: { pageSize: 10 },
       providerConfigKey: '<INTEGRATION-ID>',
       connectionId: '<CONNECTION-ID>'
   });
   
   console.log(res.data);
   

   Or fetch credentials dynamically via the Node SDK or API.

✅ You’re connected! Check the Logs tab in Nango to inspect requests.

Next step: Embed the auth flow in your app to let your users connect their Google Chat accounts

🧑‍💻 OAuth app setup

You will need to pass a Google review to go live with your integration.

Follow our guide to get approved as fast as possible.

1. Create a Google Cloud account

   If you don’t already have one, sign up for a Google Cloud account.

2. Create a new project

   1. Go to the Google Cloud Console.
   2. Click on the project dropdown at the top left of the page.
   3. Click New Project.
   4. Enter a Project Name for your project.
   5. Under Location, select the appropriate organization or folder where this project should belong.
      If you’re not part of an organization, it will default to No organization
   6. Click Create and wait for the project to be created.
   7. Select it from the project dropdown.
3. Enable the APIs you need

   1. Go to the API Library in the Google Cloud Console.
   2. Search for Google Chat API and select it, then click Enable.
4. Configure the OAuth consent screen

   1. Go to APIs & Services > OAuth consent screen in the Google Cloud Console.
   2. Click Get started.
   3. Fill in all the required fields in the App Information form.
   4. Click Next. Select the appropriate Audience:
      • External: For applications available to any Google user
      • Internal: For applications restricted to users within your Google Workspace organization
   5. Click Next. Fill in the Contact Information; these are the email addresses that Google will use to notify you about any changes to your project.
   6. Click Next, then check the I agree to the Google API Services: User Data Policy checkbox, and click Continue.
   7. Add the scopes your application needs. Under Data Access, click Add or Remove Scopes and select the scopes that correspond to the APIs you enabled.
   8. Under Audience, click Add users if you selected External user type (required for testing before verification).
5. Create OAuth 2.0 credentials

   1. Go to APIs & Services > Credentials in the Google Cloud Console.
   2. Click Create Credentials and select OAuth client ID.
   3. Select Web application as the application type.
   4. Enter a name for your OAuth client.
   5. Under Authorized redirect URIs, add https://api.nango.dev/oauth/callback.
   6. Click Create.
   7. A dialog will appear with your client ID and client secret. Save these credentials securely as you’ll need them when configuring your integration in Nango.
6. Start building your integration

   Follow the Quickstart to build your integration.

7. Verify your app

   Most Google Chat scopes are marked “sensitive” or “restricted” by Google. You need to pass a Google review to go live.

   Follow our guide to prepare and pass as quickly as possible.

8. Publish your app (switch from Testing to Production)

   To move your OAuth app from testing to production:

   1. Go to APIs & Services > OAuth consent screen > Audience.
   2. Click Publish App to switch your app from testing to production.

Common Scopes

Scope	Description
openid	Access to basic profile information
profile	Access to user’s basic profile information
email	Access to user’s email address
https://www.googleapis.com/auth/chat.messages	See, compose, send, update, and delete messages as well as their message content; add, see, and delete reactions to messages from Google Chat
https://www.googleapis.com/auth/chat.messages.create	Compose and send messages in Google Chat
https://www.googleapis.com/auth/chat.memberships.readonly	View members in Google Chat conversations
https://www.googleapis.com/auth/chat.spaces.readonly	View chat and spaces in Google Chat
https://www.googleapis.com/auth/chat.users.spacesettings	Read and update your space settings
https://www.googleapis.com/auth/chat.messages.readonly	See messages as well as their reactions and message content in Google Chat

🔗 Useful links

Useful links

Topic	Links
General	Google Cloud Console
	Google Cloud Documentation
Developer	OAuth 2.0 Documentation
	Using OAuth 2.0 for Web Server Applications
	OAuth 2.0 Scopes for Google APIs
	API Library
	OAuth Consent Screen Configuration
	Credentials Management
	App Verification Requirements
	OAuth Token Expiration
	Google Chat API

Contribute useful links by editing this page

🚨 API gotchas

API gotchas

• From the scopes page, make sure to select scopes based on the APIs you enabled earlier when setting up the app.
• Under certain circumstances, Google expires a user’s refresh token and the token refresh in Nango will fail. You can find a list of reasons from Google here, including:

1. The user has revoked your app’s access.
2. The user changed passwords and the refresh token contains Gmail scopes.
3. The user account has exceeded a maximum number of granted (live) refresh tokens.
4. The user granted time-based access to your app and the access expired.
5. If an admin set any of the services requested in your app’s scopes to Restricted.
6. For Google Cloud Platform APIs - the session length set by the admin could have been exceeded.
7. In “Testing” mode with an external user type, refresh tokens expire in 7 days unless only basic scopes are used — userinfo.email, userinfo.profile, openid, or their OpenID Connect equivalents. You can remove this 7-day limit by switch from Testing to Production. Follow step 6 in the Setup Guide above.
8. Google allows up to 100 refresh tokens per account per OAuth client ID; new tokens overwrite the oldest without warning when the limit is reached.

• While setting up the OAuth credentials, the Authorized JavaScript origins should be your site URL (https://app.nango.dev if you’re testing from the Nango UI).
• For applications using sensitive or restricted scopes, Google requires verification and a security assessment. This process can take several weeks to complete.
• Google’s OAuth consent screen has different configurations for “External” and “Internal” user types. Internal is only available for Google Workspace users and limits access to users within your organization.
• Google implements incremental authorization, allowing you to request additional scopes over time without requiring users to re-authorize all previously granted scopes.
• Google enforces rate limits on API requests, which vary depending on the specific API being used.

• Google Chat API is only available to Google Workspace users.

Contribute API gotchas by editing this page

Questions? Join us in the Slack community.