romtuck/openclaw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: clarify google chat oauth setup

Browse Source
This commit is contained in:
iHildy 2026-01-26 20:16:30 -06:00
parent 66c10e9562
commit 9a33c15743
1 changed files with 15 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
docs/channels/googlechat.md
View File

@ -5,9 +5,7 @@ read_when:
--- ---
# Google Chat (Chat API) # Google Chat (Chat API)
Status: ready for DMs + spaces via Google Chat API webhooks (HTTP only). ## Service Account Setup
## Quick setup (beginner)
1) Create a Google Cloud project and enable the **Google Chat API**. 1) Create a Google Cloud project and enable the **Google Chat API**.
- Go to: [Google Chat API Credentials](https://console.cloud.google.com/apis/api/chat.googleapis.com/credentials) - Go to: [Google Chat API Credentials](https://console.cloud.google.com/apis/api/chat.googleapis.com/credentials)
- Enable the API if it is not already enabled. - Enable the API if it is not already enabled.
@ -47,7 +45,7 @@ Status: ready for DMs + spaces via Google Chat API webhooks (HTTP only).
9) Start the gateway. Google Chat will POST to your webhook path. 9) Start the gateway. Google Chat will POST to your webhook path.
## User OAuth (optional, enables reactions) ## User OAuth (optional, enables reactions)
Service accounts cover most bot workflows, but **reactions and user-attributed actions require user OAuth**. Service account covers almost all features, but **reactions and user-attributed actions require user OAuth**.
### Option A: Use gog OAuth (recommended if you already use `gog`) ### Option A: Use gog OAuth (recommended if you already use `gog`)
If you already use `gog` for Google Workspace, you can reuse its OAuth client + refresh token. If you already use `gog` for Google Workspace, you can reuse its OAuth client + refresh token.
@ -55,8 +53,6 @@ If you already use `gog` for Google Workspace, you can reuse its OAuth client +
1) Ensure `gog` is already authorized: 1) Ensure `gog` is already authorized:
```bash ```bash
gog auth credentials /path/to/client_secret.json
gog auth add you@example.com --services gmail,calendar,drive,contacts,docs,sheets
gog auth list gog auth list
``` ```
2) Configure Google Chat to reuse `gog`: 2) Configure Google Chat to reuse `gog`:
@ -77,12 +73,23 @@ If you already use `gog` for Google Workspace, you can reuse its OAuth client +
- For headless systems (systemd, SSH-only), switch to file keyring + password (see `gog` docs). - For headless systems (systemd, SSH-only), switch to file keyring + password (see `gog` docs).
- Set `GOG_KEYRING_BACKEND=file` and `GOG_KEYRING_PASSWORD=...` for the gateway service. - Set `GOG_KEYRING_BACKEND=file` and `GOG_KEYRING_PASSWORD=...` for the gateway service.
- The file keyring lives under your gog config directory (for example `~/.config/gogcli/keyring/`). - The file keyring lives under your gog config directory (for example `~/.config/gogcli/keyring/`).
4) Verify `gog` is visible to the gateway user: 4) Verify `gog` is visible to clawdbot and ask it to run:
```bash ```bash
gog auth tokens list --json Run `gog auth tokens list --json` and tell me if you can access services.
``` ```
This lists token keys only (no secrets). If this fails, install `gog` on the gateway host and ensure the keyring is accessible. This lists token keys only (no secrets). If this fails, install `gog` on the gateway host and ensure the keyring is accessible.
For non-interactive services, set `GOG_KEYRING_PASSWORD` in the gateway environment so `gog` can unlock the keyring. For non-interactive services, set `GOG_KEYRING_PASSWORD` in the gateway environment so `gog` can unlock the keyring.
5) Set `typingIndicator` to "reaction" in your clawdbot config.
```json5
{
channels: {
"googlechat": {
actions: { reactions: true },
typingIndicator: "message",
}
}
}
```
Clawdbot reads `gog` OAuth client files from: Clawdbot reads `gog` OAuth client files from:
- `~/.config/gogcli/credentials.json` - `~/.config/gogcli/credentials.json`