Hermes BibleUnofficial Docs
← All docs Docs / Messaging Platforms

Google Chat

Google Chat Setup Connect Hermes Agent to Google Chat as a bot. The integration uses Cloud Pub/Sub pull subscriptions for inbound events and the Chat REST API f

Messaging Platforms
Section
Messaging Platforms
Source
hermesbible.com/docs/user-guide/messaging/google_chat

Google Chat Setup Connect Hermes Agent to Google Chat as a bot. The integration uses Cloud Pub/Sub pull subscriptions for inbound events and the Chat REST API f

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. Overview
  2. Step 1: Create or pick a GCP project
  3. Step 2: Enable two APIs
  4. Step 3: Create a Service Account
  5. Step 4: Create the Pub/Sub topic and subscription
  6. Step 5: IAM binding on the topic (critical)
  7. Step 6: IAM binding on the subscription
  8. Step 7: Configure the Chat app
  9. Step 8: Install the bot in a test space
  10. Step 9: Configure Hermes
  11. Formatting and capabilities
  12. Step 10: Native attachment delivery (optional)
  13. Why a separate flow
  14. One-time setup (per profile)

Section map

Overview

Maps overview to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Step 1: Create or pick a GCP project

Maps step 1: create or pick a gcp project to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Step 2: Enable two APIs

Maps step 2: enable two apis to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Step 3: Create a Service Account

Maps step 3: create a service account to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Step 4: Create the Pub/Sub topic and subscription

Maps step 4: create the pub/sub topic and subscription to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Step 5: IAM binding on the topic (critical)

Maps step 5: iam binding on the topic (critical) to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Step 6: IAM binding on the subscription

Maps step 6: iam binding on the subscription to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Step 7: Configure the Chat app

Maps step 7: configure the chat app to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Messaging Platforms doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: Overview, Step 1: Create or pick a GCP project, Step 2: Enable two APIs, Step 3: Create a Service Account, Step 4: Create the Pub/Sub topic and subscription. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: google, setup, connect, integration, cloud. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitMessaging Platforms documentation

Use when you need orientation for google chat before applying exact upstream commands.

Verify firstOverview

Open the source anchor for Overview and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Messaging Platforms, then open the linked source page for exact current syntax.
  2. Start with the source section for Overview; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Step 1: Create or pick a GCP project if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Model spend

Set provider, token, and retry limits before scaling the workflow beyond a single test run.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page