OpenClaw RingCentral Channel

RingCentral Team Messaging channel plugin for OpenClaw.

Features

• Bot Add-in WebSocket ingress and outbound replies
• Optional owner JWT credentials for owner-observed groups, history reads, and fallback sends
• OpenClaw channel ingress policy for DM/group allowlists, pairing, mention gates, and ignored/allowed channels
• Threaded replies with off, first, and all modes
• Inbound file/image attachments are downloaded into OpenClaw managed media storage after admission
• Optional processing placeholder while an agent run is active
• Shared OpenClaw message actions for send/read/edit/delete/channel-info
• Optional ringcentral_get_recent_messages agent tool

Configuration

Minimal bot-only config:

{
  "channels": {
    "ringcentral": {
      "enabled": true,
      "botToken": "your-bot-static-token"
    }
  }
}

Owner credentials for history/fallback:

{
  "channels": {
    "ringcentral": {
      "enabled": true,
      "botToken": "your-bot-static-token",
      "ownerCredentials": {
        "clientId": "your-client-id",
        "clientSecret": "your-client-secret",
        "jwt": "your-owner-jwt-token"
      }
    }
  },
  "tools": {
    "allow": ["ringcentral_get_recent_messages"]
  }
}

credentials is still accepted as a deprecated config alias for ownerCredentials.

Environment

Use RC_* variables only. Existing RINGCENTRAL_* variables are intentionally ignored.

| Variable | Description | | --- | --- | | RC_BOT_TOKEN | Bot static token | | RC_SERVER_URL | API server URL, default https://platform.ringcentral.com | | RC_USER_CLIENT_ID | Owner REST API app client ID | | RC_USER_CLIENT_SECRET | Owner REST API app client secret | | RC_USER_JWT_TOKEN | Owner JWT token | | RC_ALLOWED_USER_EMAILS | Comma-separated DM/user allowlist aliases | | RC_ALLOW_ALL_USERS | Allow all DM senders | | RC_ALLOWED_CHANNELS | Comma-separated chat IDs allowed for group/channel ingress | | RC_IGNORED_CHANNELS | Comma-separated chat IDs ignored for ingress | | RC_REQUIRE_MENTION | Require mention in groups, default true | | RC_FREE_RESPONSE_CHANNELS | Channels that do not require mentions | | RC_THREAD_REQUIRE_MENTION | Require mention in thread follow-ups, default true | | RC_NO_THREAD_CHANNELS | Channels where replies must be unthreaded | | RC_REPLY_TO_MODE | off, first, or all; default first | | RC_PROCESSING_EMOJI_ENABLED | Enable processing placeholder, default true | | RC_PROCESSING_EMOJI_EDIT_DELAY_SECONDS | Delay before placeholder update | | RC_ATTACHMENT_DOWNLOAD_ENABLED | Download admitted inbound attachments, default true | | RC_ATTACHMENT_MAX_COUNT | Max attachments per inbound message, default 5 | | RC_ATTACHMENT_MAX_BYTES | Max bytes per downloaded attachment, default 5242880 | | RC_HISTORY_MESSAGE_LIMIT | Default history record count, max 1000 | | RC_HOME_CHANNEL | Default history/home chat ID | | RC_HOME_CHANNEL_NAME | Display name for the home chat |

Key Options

| Option | Default | Description | | --- | --- | --- | | groupPolicy | disabled | disabled, allowlist, or open | | groups.<chatId>.enabled | true | Enable an allowlisted group | | groups.<chatId>.requireMention | inherited | Per-group mention gate | | groups.<chatId>.users | [] | Per-group sender allowlist | | dm.policy | open | disabled, allowlist, pairing, or open | | dm.allowFrom | [] | Stable sender IDs allowed in DMs | | replyToMode | first | Threading behavior for replies | | noThreadChannels | [] | Chat IDs that force unthreaded sends | | attachments.enabled | true | Download admitted RingCentral file/image attachments | | attachments.maxCount | 5 | Max attachments to process per inbound message | | attachments.maxBytes | 5242880 | Max bytes per downloaded attachment | | allowBots | false | Allow bot-authored inbound messages |

When owner credentials are configured and no explicit DM allowlist is provided, the effective default is owner-only unless allowAllUsers is enabled.

RingCentral Setup

1. Create a RingCentral Bot Add-in app with Team Messaging and WebSocket Subscriptions permissions.
2. Copy the bot static token into botToken or RC_BOT_TOKEN.
3. Optionally create a JWT REST API app for the owner user with Team Messaging, WebSocket Subscriptions, Read Accounts, and Read Messages permissions.
4. Put owner app credentials in ownerCredentials or RC_USER_*.

Agent Actions

The shared OpenClaw message tool exposes these RingCentral actions when configured:

| Action | Description | | --- | --- | | send | Send a message | | read | Read recent messages | | edit | Edit a message | | delete | Delete a message | | channel-info | Read chat metadata |

The optional ringcentral_get_recent_messages tool reads recent messages through owner credentials. Enable it explicitly with tools.allow.

Verification

pnpm test
pnpm typecheck

Live Smoke Test

The GitHub Actions workflow RingCentral Live Smoke validates the real RingCentral API path without starting OpenClaw and without any LLM secrets.

Configure the GitHub Environment ringcentral-live with these secrets:

| Secret | Description | | --- | --- | | RC_BOT_TOKEN | Bot static token used to send and delete the test message | | RC_USER_CLIENT_ID | Owner JWT app client ID | | RC_USER_CLIENT_SECRET | Owner JWT app client secret | | RC_USER_JWT_TOKEN | Owner JWT token used to read recent history | | RC_E2E_CHAT_ID | Test chat/group ID | | RC_SERVER_URL | Optional API server URL, default https://platform.ringcentral.com |

Run the workflow manually from GitHub Actions. It sends a unique test message, reads it back through owner history, exercises ringcentral_get_recent_messages, and deletes the test message by default.

Local live verification is also available:

RC_E2E_ENABLED=true \
RC_BOT_TOKEN=... \
RC_USER_CLIENT_ID=... \
RC_USER_CLIENT_SECRET=... \
RC_USER_JWT_TOKEN=... \
RC_E2E_CHAT_ID=... \
pnpm test:live:ringcentral

License

MIT