How Do I Connect the Google Chat Integration?

Last updated: August 26, 2026

With the Google Chat integration, you grant Pylon's service account domain-wide delegation once and supply Pylon with a dedicated admin account (the integration user). Pylon acts as that account in the spaces you link to read and send messages in your linked Google Chat spaces.

Before you start

  • You must be a super administrator of your Google Workspace domain. Only a super admin can grant domain-wide delegation.

  • Create or choose a dedicated admin Workspace account (or the Integration User) for Pylon to act as. Pylon adds this account to every space you link.

  • The integration user's email must be on the same domain as your Pylon login email.

Step 1: Grant domain-wide delegation in Google Admin console

  1. In the Google Admin console, open Domain-wide delegation (Security → Access and data control → API controls), then click Add new.

  2. Enter the client ID for your Pylon region. The Pylon modal shows the correct one for you:

    Pylon region

    Client ID

    US

    104383803000843198070

    EU

    110213122751103181763

  3. Paste all nine scopes below into the OAuth scopes field as one comma-separated list. To see why we need each scope, check out the What each scope is for section below

    https://www.googleapis.com/auth/chat.messages,https://www.googleapis.com/auth/chat.messages.reactions,https://www.googleapis.com/auth/chat.spaces,https://www.googleapis.com/auth/chat.memberships,https://www.googleapis.com/auth/admin.directory.user.readonly,https://www.googleapis.com/auth/chat.admin.spaces.readonly,https://www.googleapis.com/auth/chat.admin.memberships.readonly,https://www.googleapis.com/auth/chat.admin.memberships,https://www.googleapis.com/auth/contacts.other.readonly

  4. Click Authorize.

Step 2: Start the connection in Pylon

  1. Go to Integrations → Google Chat → Connect.

  2. Review the prerequisites screen, then click Continue.

  3. Enter your integration user's email and click Connect.

Pylon immediately verifies, as that account, that it can read Google Chat, read your Workspace directory, and read Google Contacts. If any check fails the connection is not saved, and the error names the scope to add. Fix the grant and try again - changes to a delegation grant can take a few minutes to take effect.

Step 3: Link spaces to accounts

After connecting the Google Chat integration, chat spaces should start automatically populating in account linking workflows. Spaces are linked to accounts individually, from the Accounts page.

  1. Navigate to the Accounts page

  2. Either click Add Account → Google Chat spaces or click on an existing account and navigate to External channels

Once a space is linked, new messages in it create and update Pylon issues, and replies from Pylon post back into the space.

What each scope is for

Scope

Why Pylon needs it

chat.messages

Read incoming messages and post replies in linked spaces

chat.messages.reactions

Sync emoji reactions in both directions

chat.spaces

List your spaces so you can pick which to link

chat.memberships

Read who is in a space

admin.directory.user.readonly

Resolve senders in your domain to their email

chat.admin.spaces.readonly

Discover spaces the integration user has not joined yet

chat.admin.memberships.readonly and chat.admin.memberships

Add the integration user to a space you link, so you do not have to invite it by hand

contacts.other.readonly

Identify guests from outside your domain

Notes and limitations

  • Only spaces your integration user belongs to can be linked. Pylon adds that account to each space at link time.

  • To change the integration user, navigate to Integrations → Google Chat and change the integration user. This will automatically update any existing dependencies to use the new integration user and add it to all existing linked chats

  • Direct messages and group chats are not linkable at this point