/docs/integrations/

Integrations

Give your bot access to external services by adding integration tokens in the ClawBlitz dashboard.

How Integrations Work

Integration tokens are set as environment variables in your OpenClaw instance. Once a token is saved, your bot restarts automatically (about 15-30 seconds) and the corresponding skill becomes active. You just talk to the bot naturally and it will use the right tool.

All tokens are stored encrypted and are only accessible by your bot's runtime environment.

Removing an Integration

To remove an integration, type clear into the token field in the dashboard and click Save. This deletes the token from your environment and disables the integration. The exact value clear is a special keyword — it does not set the token to the literal string "clear", it removes it entirely.

Integration Overview

Service Token(s) Required Dashboard Field
Notion NOTION_API_KEY 1 field
GitHub GH_TOKEN 1 field
X / Twitter X_API_KEY, X_API_SECRET, X_ACCESS_TOKEN, X_ACCESS_SECRET 4 fields
Trello TRELLO_API_KEY, TRELLO_TOKEN 2 fields
Gmail GOG_ACCOUNT, GOG_KEYRING_PASSWORD (OAuth + keyring) 2 fields

Notion

Connect your bot to Notion so it can read, create, and update pages and databases in your workspace.

Getting Your Notion API Key

  1. Go to Notion Internal Integrations
  2. Click New integration
  3. Give it a name (e.g., "ClawBlitz Bot") and select the workspace
  4. Under Capabilities, ensure it has Read, Update, and Insert content permissions
  5. Click Submit and copy the Internal Integration Secret

Share Pages with the Integration

The integration can only access pages you explicitly share with it. There are two ways to do this:

  • From the integration: Go to your integration's Content access tab and click Edit access to select which pages and databases to share
  • From a page: Open any Notion page or database, click the ... menu in the top right, select Connections, and add your integration

Your bot will only be able to read and write pages that have been shared. If it says it can't access your workspace, this is almost always the reason.

Provider Compatibility

The Notion integration works best with Anthropic (Claude) as your AI provider. Some providers (e.g., OpenAI) may refuse to execute API calls with tokens for security reasons. If your bot says it "can't access Notion" or "can't run commands with sensitive data," switch to Anthropic in your dashboard configuration.

# Paste into the Notion API Key field on your dashboard
ntn_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

GitHub

Connect your bot to GitHub so it can interact with repositories, issues, pull requests, and more.

Getting Your GitHub Token

  1. Go to GitHub Settings > Developer settings > Personal access tokens
  2. Click Generate new token (select Fine-grained for better security)
  3. Set an expiration date and a descriptive name
  4. Select the repositories you want the bot to access
  5. Grant permissions based on what you need:
    • • Contents — read/write to read and push code
    • • Issues — read/write to manage issues
    • • Pull requests — read/write to manage PRs
    • • Metadata — read-only (required for all tokens)
  6. Click Generate token and copy it
# Paste into the GitHub Token field on your dashboard
github_pat_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Classic tokens (starting with ghp_) also work, but fine-grained tokens are recommended for least-privilege access.

X / Twitter

The X/Twitter integration requires four separate credentials. This allows your bot to post tweets, read timelines, and interact with the X platform on your behalf.

Getting Your X Credentials

  1. Go to the X Developer Portal
  2. Create a project and an app within it (you need at least Basic access)
  3. In your app settings, go to Keys and Tokens
  4. Under Consumer Keys, generate and copy:
    • • API Key → X_API_KEY
    • • API Key Secret → X_API_SECRET
  5. Under Authentication Tokens, generate and copy:
    • • Access Token → X_ACCESS_TOKEN
    • • Access Token Secret → X_ACCESS_SECRET
  6. Make sure your app has Read and Write permissions under User authentication settings
# Paste each value into its matching field on your dashboard
API Key: xxxxxxxxxxxxxxxxxxxxxxxxx
API Secret: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Access Token: 1234567890-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Access Secret: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

All four tokens must be present for the X integration to work. If any are missing, the skill will be inactive.

Trello

Connect your bot to Trello so it can manage boards, lists, and cards.

Getting Your Trello Credentials

  1. Go to trello.com/power-ups/admin
  2. Click New to create a new Power-Up (or use an existing one)
  3. After creating, click on your Power-Up and go to the API Key tab
  4. Copy your API Key
  5. On the same page, click the Token link to generate a token
  6. Authorize the app and copy the token
# Paste each value into its matching field on your dashboard
API Key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Gmail

Connect your bot to Gmail so it can read and send emails on your behalf. Gmail uses gogcli (Google OAuth CLI) for authentication. Because your bot runs in a headless environment with no browser, the OAuth flow must be completed on your local machine first.

Step 1: Create Google OAuth Credentials

  1. Go to the Google Cloud Console and create a project (or use an existing one)
  2. Enable the Gmail API for your project
  3. Go to Credentials and create an OAuth 2.0 Client ID (choose "Desktop app" as the application type)
  4. Download the credentials JSON file

Step 2: Authenticate on Your Local Machine

  1. Install gogcli on your local machine (npm i -g gogcli)
  2. Set a GOG_KEYRING_PASSWORD environment variable — this is the password that encrypts your OAuth tokens:
    # Pick any strong password and remember it
    export GOG_KEYRING_PASSWORD="YourStrongPassword123"
  3. Run gog auth add --remote to start the OAuth flow — this opens your browser for Google sign-in and stores the encrypted tokens locally

Step 3: Transfer Credentials to Your Bot

  1. After authenticating, provide the resulting credential files to your bot via chat — the bot will tell you what files it needs
  2. In your ClawBlitz dashboard, go to the Integrations section and set the Google Keyring Password field to the exact same password you used for GOG_KEYRING_PASSWORD on your local machine
  3. Click Save

Critical: The GOG_KEYRING_PASSWORD on the dashboard must match the password you used when running gog auth add on your local machine. If they don't match, your bot won't be able to decrypt the OAuth tokens and Gmail will fail silently.

Note: Once authenticated and the keyring password is set correctly, Gmail works in both interactive sessions and cron jobs. You do not need to re-authorize unless the credentials expire or are revoked. If you leave the Google Keyring Password field blank, a default value is auto-generated for you — but you must use that same value locally when authenticating.

Removing Integrations

To disconnect a service, use the special clear keyword:

  1. Open the ClawBlitz dashboard and go to the integration you want to remove
  2. Type clear into the token field (or all token fields for multi-token integrations)
  3. Click Save

This removes the token from your environment entirely. The word "clear" is treated as a command, not stored as a value. You should also revoke the token on the respective platform's settings page to fully deauthorize it.