Reference · built on requestConnectorMessaging & notifications

Google Chat

Spaces, messages, and memberships in Google Workspace through the Google Chat API, with events over Pub/Sub.

Request accessPricing ↗

About

Google Chat is the messaging service inside Google Workspace: spaces, group conversations, direct messages, and threads. The Chat API at chat.googleapis.com exposes spaces, spaces.messages, spaces.members, spaces.messages.reactions, spaces.spaceEvents, and media. A Chat app runs from a Google Cloud project with the Chat API enabled and authenticates either as itself with a service account or as a user through OAuth 2.0; each method accepts one type or both. Events arrive as interaction events at an HTTP endpoint or a Pub/Sub topic, or as Google Workspace Events API subscriptions on a space.

Through Fibric, an operator reads the spaces the app belongs to and proposes a message, a thread reply, or a reaction for a person to approve.

This is a reference listing. It documents what Fibric would read from Google Chat and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Messages in a space through spaces.messages.list and spaces.messages.get
  • Space and roster records through spaces.list, spaces.get, and spaces.members.list
  • Interaction events when a user @mentions the app or adds it to a space, delivered to an HTTP endpoint or Pub/Sub
  • Workspace Events API subscriptions such as google.workspace.chat.message.v1.created and membership.v1.created
  • Recent history through spaces.spaceEvents.list, for periodic catch-up or recovery after an outage
  • Attachments through spaces.messages.attachments.get and media.download

Proposed actions

  • Target capability: propose a text or card message with spaces.messages.create, up to 32,000 bytes
  • Target capability: propose a reply into an existing thread using messageReplyOption
  • Target capability: propose editing or deleting a message the app sent with spaces.messages.patch or delete
  • Target capability: propose a reaction with spaces.messages.reactions.create under user authentication
  • Target capability: propose adding a member to a space with spaces.members.create

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Morning brief in the operations space

    A card with yesterday's exceptions posts to your operations space at the hour you choose. The operator drafts it, a person releases it, and it is threaded so replies stay attached.

    With Morning Brief

  • Deadline warnings in a thread

    When a ticket nears its deadline, the operator proposes a message in the team's space with the ticket link. A reply in the thread records who took it.

    With Breach Watch, Exception Digest

  • Open actions gathered into one message

    Commitments made in earlier posts are collected and re-surfaced as a single message with each owner @mentioned, once a person approves the list.

    With Action Follow-up

Requirements

  • A Business or Enterprise Google Workspace account with access to Google Chat
  • A Google Cloud project with the Chat API enabled and a configured Chat app
  • For app authentication: a service account, and the app added as a member of each space it reads or posts in
  • For chat.app.* scopes or domain-wide delegation: a one-time approval by a Google Workspace administrator
Authentication
App authentication with a service account, or user authentication through OAuth 2.0 with scopes such as chat.messages, chat.spaces, and chat.memberships, from a Google Cloud project with the Chat API enabled.

Limits

  • Per project: 3,000 message writes and 3,000 message reads per 60 seconds, and 60 space writes per 60 seconds
  • Per space: 1 write per second, 15 reads per second, and 5 reaction writes per second
  • Incoming webhooks post only, cannot read, and share 1 request per second across all webhooks in a space
  • Over quota the API returns 429; Google recommends exponential backoff

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Google Chat ↗

Questions and answers

Does the app need to be in a space to read it?
Under app authentication, yes: the Chat app must be a member of the space. Under user authentication the API returns what that user can see. Methods differ in which type they accept, and a method that accepts both returns different results depending on the type used.
How do events reach Fibric?
Two ways. Interaction events fire when a user @mentions the app or adds it to a space and are delivered to an HTTP endpoint or a Pub/Sub topic. Google Workspace Events API subscriptions deliver message, membership, reaction, and space events for a space to a Pub/Sub topic in CloudEvent format.
What are the write limits?
3,000 message writes per 60 seconds per Google Cloud project, 60 space writes per 60 seconds, and 1 write per second per space. Message size is capped at 32,000 bytes including cards. Over quota, the API returns 429 and Google recommends exponential backoff.
Ask about Google Chat

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Google Chat through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy