Google Chat

Google Chat connects differently than Slack or Discord. Google Chat apps have no equivalent of Slack's "Add to Slack" OAuth button for installing across an arbitrary customer's Workspace — instead, you generate a one-time connect code in AnswerLoops, add the AnswerLoops app to a Chat space yourself, and post the code there to pair the two.

Prerequisites

The platform operator must have a Google Chat app configured and GOOGLE_CHAT_SERVICE_ACCOUNT_JSON + GOOGLE_CHAT_ENDPOINT_URL set. See Google Chat App Setup for the one-time Google Cloud configuration.

How it works

1. Go to Settings → Integrations → Google Chat and click Generate connect code
2. Add the AnswerLoops app to a Google Chat space (your Workspace admin may need to enable third-party Chat apps first — see the setup guide)
3. Post /connect <code> in that space
4. AnswerLoops pairs the space to your org — the Settings page shows Connected once it succeeds
5. Questions posted in that space now flow into the same AI pipeline as every other channel

Shared capabilities

Same pipeline as every other channel:

• AI deflection with configurable confidence threshold
• Ticket creation + deduplication
• Thread-aware replies (a reply inside a Google Chat thread appends to its ticket instead of creating a new one)
• Escalation mention when AI confidence is low — set an escalation user's Chat resource id (users/12345) in Settings

What's different from Slack/Discord

• No bot token per org. Sending replies authenticates as a single AnswerLoops-owned service account shared by every connected org — there's nothing to paste or rotate per workspace.
• No OAuth callback. Pairing is the connect-code flow above, not a redirect-based "Add to Slack"-style install.
• No role/group mentions. Google Chat has no Discord role or Slack usergroup equivalent — escalation targets one specific user.

Setup guide

See Google Chat App Setup for the platform-operator-side Google Cloud configuration.