Google Chat

!Google Chat

Access Google Chat via the Google Chat API with OAuth authentication. Manage spaces, members, messages, attachments, and threaded conversations.

This skill uses ClawLink for hosted connection flows and credentials so you do not need to configure Google Chat API access yourself.

Setup in 3 Steps

How It Works

┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐
│   OpenClaw      │────▶│   ClawLink   │────▶│  Google Chat API │
│   (User Chat)   │     │   (OAuth)    │     │   (REST)         │
└─────────────────┘     └──────────────┘     └──────────────────┘
         │                       │                       │
         │  1. Install Plugin    │                       │
         │  2. Pair Device       │                       │
         │  3. Connect Google Chat                        │
         │                       │  4. Secure Token      │
         │                       │  5. Proxy Requests    │
         │                       │                       │
         ▼                       ▼                       ▼
   ┌──────────┐           ┌──────────┐           ┌──────────┐
   │  SKILL   │           │ Dashboard│           │ Google   │
   │  File    │           │ Auth     │           │ Chat     │
   └──────────┘           └──────────┘           └──────────┘

Install

Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.

openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart

Then tell the user: "OpenClaw has been restarted. Send /new as a standalone message to start a fresh chat, then ask for Google Chat again."

Quick Start

# List spaces the user is member of
clawlink_call_tool --tool "google_chat_list_spaces" --params '{}'

# List members in a space
clawlink_call_tool --tool "google_chat_list_members" --params '{"parent": "spaces/space-id"}'

# Send a message to a space
clawlink_call_tool --tool "google_chat_create_message" --params '{"parent": "spaces/space-id", "text": "Hello from OpenClaw!"}'

Authentication

All Google Chat tool calls are authenticated automatically by ClawLink using the user's connected Google account.

No API key is required in chat. ClawLink stores the OAuth token securely and injects it into every Google Chat API request on the user's behalf.

Getting Connected

1. Install the ClawLink plugin (see Install above).
2. Pair the plugin with clawlink_begin_pairing if it is not configured yet.
3. Open https://claw-link.dev/dashboard?add=google-chat and connect Google Chat.
4. Call clawlink_list_integrations to verify the connection is active.

Connection Management

List Connections

clawlink_list_integrations

Response: Returns all connected integrations. Look for google-chat in the list.

Verify Connection

clawlink_list_tools --integration google-chat

Response: Returns the live tool catalog for Google Chat.

Reconnect

If Google Chat tools are missing or the connection shows an error:

1. Direct the user to https://claw-link.dev/dashboard?add=google-chat
2. After they confirm, call clawlink_list_integrations to verify
3. Then call clawlink_list_tools --integration google-chat

Security & Permissions

• Access is scoped to Google Chat spaces and messages accessible to the connected Google account.
• All write operations require explicit user confirmation. Before executing any message send, space create, or member change, confirm the intended effect with the user.
• Destructive actions (deleting spaces, removing members) are marked as high-impact and must be confirmed.
• Message size is limited to 32,000 bytes. Card-based messages require bot authentication.

Tool Reference

Spaces

Members

Messages

Reactions

Attachments & Custom Emoji

Sections

Code Examples

List spaces

clawlink_call_tool --tool "google_chat_list_spaces" \
  --params '{}'

Send a message to a space

clawlink_call_tool --tool "google_chat_create_message" \
  --params '{
    "parent": "spaces/space-id",
    "text": "Hello team! Just wanted to share an update on the project status."
  }'

Reply in a thread

clawlink_call_tool --tool "google_chat_create_message" \
  --params '{
    "parent": "spaces/space-id",
    "text": "Thanks for the update!",
    "thread": {
      "thread_key": "original-message-id"
    }
  }'

Add a reaction to a message

clawlink_call_tool --tool "google_chat_create_reaction" \
  --params '{
    "parent": "spaces/space-id/messages/message-id",
    "emoji_unicode": "👍"
  }'

Discovery Workflow

1. Call clawlink_list_integrations to confirm Google Chat is connected.
2. Call clawlink_list_tools --integration google-chat to see the live catalog.
3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.
4. If the user describes a capability but the exact tool is unclear, call clawlink_search_tools with a short query and integration google-chat.
5. If no Google Chat tools appear, direct the user to https://claw-link.dev/dashboard?add=google-chat.

Execution Workflow

┌─────────────────────────────────────────────────────────────┐
│  READ OPERATIONS (Safe)                                     │
│  list → get → search → describe → call                      │
│                                                             │
│  Example: List spaces → Get space → Show members            │
└─────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────┐
│  WRITE OPERATIONS (Require Confirmation)                    │
│  list → get → describe → preview → confirm → call           │
│                                                             │
│  Example: Preview message → User confirms → Execute send    │
└─────────────────────────────────────────────────────────────┘

1. For unfamiliar tools, ambiguous requests, or any write action, call clawlink_describe_tool first.
2. Use the returned guidance, schema, whenToUse, askBefore, safeDefaults, examples, and followups to shape the call.
3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.
4. For writes or anything marked as requiring confirmation, call clawlink_preview_tool first.
5. Execute with clawlink_call_tool. Pass confirmation only after the preview matches the user's intent.
6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.

Notes

• Space names use format spaces/space-id in API calls.
• Message threading uses thread_key to reply to existing threads.
• Custom emojis are only available for Google Workspace accounts and require admin enablement.
• With user authentication, only plain text messages are supported. Card-based messages require bot authentication.
• Message size limit is 32,000 bytes.

Error Handling

Troubleshooting: Tools Not Visible

1. Check that the ClawLink plugin is installed:

```bash

openclaw plugins list

```

1. If the plugin is installed but tools are missing, tell the user to send /new as a standalone message to reload the catalog.
2. If a fresh chat does not help, run:

```bash

openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json

openclaw gateway restart

```

1. After restart, tell the user to send /new again and retry.

Troubleshooting: Invalid Tool Call

1. Ensure the integration slug is exactly google-chat.
2. Use clawlink_describe_tool to verify parameter names and types before calling.
3. For write operations, always call clawlink_preview_tool first.

Resources

• Google Chat API Reference
• Google Chat API Overview
• ClawLink
• ClawLink Docs
• ClawLink Verification

Related Skills

• Slack — For alternative team messaging
• Gmail — For email alongside chat

Powered by ClawLink — an integration hub for OpenClaw

!ClawLink Logo