Gmail Assistant

!Gmail Assistant

Access Gmail via the Gmail API with OAuth authentication. Read, search, draft, reply to, and organize Gmail from chat.

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

Setup in 3 Steps

How It Works

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

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 Gmail again."

Quick Start

# Get Gmail profile (confirms connection and shows email)
clawlink_call_tool --tool "gmail_get_profile" --params '{}'

# List recent emails
clawlink_call_tool --tool "gmail_fetch_emails" --params '{"max_results": 10}'

# Search emails
clawlink_call_tool --tool "gmail_fetch_emails" --params '{"query": "from:boss@example.com subject:report"}'

Authentication

All Gmail 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 Gmail 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=gmail and connect Gmail.
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 gmail in the list.

Verify Connection

clawlink_list_tools --integration gmail

Response: Returns the live tool catalog for Gmail.

Reconnect

If Gmail tools are missing or the connection shows an error:

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

Security & Permissions

• Access is scoped to the connected Google account's Gmail mailbox.
• All write operations require explicit user confirmation. Before executing any send, reply, forward, draft, label change, archive, or delete call, confirm the intended action with the user.
• Destructive actions (permanent delete, trash) are marked as high-impact and must be confirmed.
• Always confirm recipients, subject, and body before sending email.

Tool Reference

Email Retrieval

Sending & Drafts

Labels

Thread & Message Management

Bulk Operations

Settings & Profile

Filters

Contacts

Code Examples

Search emails from a specific sender

clawlink_call_tool --tool "gmail_fetch_emails" \
  --params '{
    "query": "from:boss@example.com",
    "max_results": 20
  }'

Send a new email

clawlink_call_tool --tool "gmail_send_email" \
  --params '{
    "to": ["recipient@example.com"],
    "subject": "Weekly Report",
    "body": "Please find the weekly report attached.",
    "is_html": false
  }'

Reply to a thread

clawlink_call_tool --tool "gmail_reply_to_thread" \
  --params '{
    "thread_id": "thread-id-here",
    "body": "Thank you for the update. I will review and get back to you shortly.",
    "incoming": false
  }'

Create a draft

clawlink_call_tool --tool "gmail_create_email_draft" \
  --params '{
    "to": ["team@example.com"],
    "subject": "Meeting Notes",
    "body": "Here are the notes from todays meeting...",
    "is_html": false
  }'

Add label to email

clawlink_call_tool --tool "gmail_add_label_to_email" \
  --params '{
    "message_id": "message-id-here",
    "label_ids": ["Label_123"]
  }'

Discovery Workflow

1. Call clawlink_list_integrations to confirm Gmail is connected.
2. Call clawlink_list_tools --integration gmail 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 gmail.
5. If no Gmail tools appear, direct the user to https://claw-link.dev/dashboard?add=gmail.

Execution Workflow

┌─────────────────────────────────────────────────────────────┐
│  READ OPERATIONS (Safe)                                     │
│  search → fetch → get → list → call                         │
│                                                             │
│  Example: Search emails → Fetch thread → Show messages      │
└─────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────┐
│  WRITE OPERATIONS (Require Confirmation)                    │
│  describe → preview → confirm → send/draft/label/trash      │
│                                                             │
│  Example: Preview email → 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.
4. For sends, replies, forwards, drafts, label changes, archive/delete, call clawlink_preview_tool first, then confirm with the user.
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

• System labels (INBOX, SENT, SPAM, TRASH) are read-only and cannot be created or deleted.
• Custom label IDs (e.g., Label_123) are required for label operations — display names cannot be used.
• The thread_id is required for replies. Leave subject empty when replying to stay in the same thread.
• Message size limit is ~25 MB including attachments. Larger attachments may fail.
• Gmail search query syntax: from:, subject:, label:, is:unread, after:, before:.

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 gmail.
2. Use clawlink_describe_tool to verify parameter names and types before calling.
3. For send, reply, forward, draft, label, archive, and delete operations, always call clawlink_preview_tool first.

Resources

• Gmail API Documentation
• Gmail API Reference
• Gmail Query Syntax
• ClawLink
• ClawLink Docs
• ClawLink Verification

Powered by ClawLink — an integration hub for OpenClaw

!ClawLink Logo