Connecting channels
Connect messaging to the older OpenClaw sandbox and check what each flow actually requires.
Start with the right runtime
The channel form in the older OpenClaw configuration page uses the account's OpenClaw sandbox. That sandbox must exist, have an ID, and be running. A LaunchPad workspace is a separate runtime record; subscribing to LaunchPad alone does not satisfy this older channel endpoint.
The channel endpoint checks the main account plan. It accepts trial, gifted, starter, pro, scale, hermes, openclaw, and both, plus the agent, network, and permanent aliases. Free and expired accounts are rejected. LaunchPad plan names are handled separately.
Telegram and Discord
Telegram
In Telegram, message @BotFather, send /newbot, and follow its prompts. In the OpenClaw configuration page, open Telegram, paste the bot token into its private field, and connect. Send your bot a message to check delivery.
Discord
Create a Discord application and bot in the Developer Portal. Enable Message Content Intent and Server Members Intent as the in-app guide directs. Paste the bot token into the private Discord field and connect. Invite the bot to your server through Discord's OAuth2 URL Generator, then test a mention or direct message.
Slack and WhatsApp have different setup paths
Slack is defined as a token-based channel in the shared connector. It requires an App-Level Token, a Bot Token, and a Signing Secret. The current configuration screen exposes Discord, Telegram, and WhatsApp controls; it does not provide a Slack form. Slack's connector definition is not evidence of a complete in-app setup flow.
WhatsApp uses the separate QR pairing flow in the configuration page. Start pairing, scan the displayed QR code using WhatsApp's linked-device flow, and wait for connected status. It uses the same plan and running-sandbox checks. Pairing can remain starting or fail if the gateway stops.
Disconnect and test again
Use Disconnect on the channel you want to remove. When the sandbox is running, the route removes that channel's configuration and restarts the gateway. It also removes stored connection metadata and the credential backup. If the sandbox is stopped or missing, only the stored records are cleared; live configuration removal is not guaranteed. Do not paste bot tokens, QR session data, or API keys into support messages.