OpenClaw AI agent supports integration with 13+ messaging platforms, allowing you to trigger automated workflows from WhatsApp, Discord, Slack, Telegram, Signal, and more. This guide shows how to configure multiple platforms simultaneously on a remote Mac, create unified command handlers, and build cross-platform automation pipelines for iOS development, CI/CD, and system administration.
Why Multi-Platform Messaging Integration?
Modern development teams use different messaging platforms for different purposes. Discord for community engagement, Slack for internal team communication, Telegram for bot automation, and WhatsApp for mobile-first workflows. Rather than maintaining separate automation systems for each platform, OpenClaw provides a unified gateway that connects all channels to a single AI agent running on your remote Mac.
With multi-platform triggers, you can send the same command from any messaging app and get consistent results. A developer can type "deploy staging" in Slack while a QA engineer sends the same command via Telegram. OpenClaw executes the build script once and streams output to both platforms. This eliminates platform lock-in and allows teams to use their preferred communication tools without sacrificing automation capabilities.
Platform Comparison Matrix
Each messaging platform has unique characteristics that affect automation capabilities. Here's a technical comparison:
| Platform | Connection Method | Best Use Case | Rate Limits |
|---|---|---|---|
| Telegram | Bot API with token | High-volume automation, unlimited free API | 30 messages/second |
| Discord | Bot application + OAuth2 | Developer communities, rich embeds | 5 requests/second per bot |
| QR pairing or Business API | Mobile-first teams, end-to-end encryption | Varies by method | |
| Slack | App with socket mode | Enterprise teams, workspace integration | 1+ request/second (tier dependent) |
| Signal | signal-cli bridge | Privacy-focused teams, secure messaging | No official rate limits |
Architecture Overview
OpenClaw Gateway runs on your remote Mac and acts as a message broker. Each messaging platform connects to the Gateway through its own protocol: Telegram uses long polling, Discord uses WebSocket, WhatsApp uses WhatsApp Web protocol, and Slack uses Socket Mode. The Gateway normalizes these into a unified message format and forwards them to the AI agent.
When a user sends a command to any platform, the Gateway receives it, authenticates the sender against the configured access policy, and routes the message to the appropriate handler. The AI agent processes the command, executes system tasks if approved, and sends responses back through the same channel. This architecture allows adding new platforms without modifying the core automation logic.
"OpenClaw's multi-platform design eliminates the need for platform-specific scripts. Write your automation once, trigger it from anywhere." — OpenClaw documentation
Prerequisites and Setup
Before configuring multi-platform integration, ensure you have:
- Remote Mac with OpenClaw installed: VNCMac dedicated instance with macOS Sequoia or later, Node.js 22+, and OpenClaw Gateway CLI.
- Platform accounts and tokens: Create bot accounts on each platform you want to integrate. For Telegram, use @BotFather. For Discord, create an application in Discord Developer Portal. For Slack, create a Slack app with Socket Mode enabled.
- SSH access and persistent session: Use tmux or Launch Agent to keep the Gateway running after SSH disconnection.
- Network access: Ensure outbound HTTPS (443) is allowed for API connections. Some platforms require WebSocket support.
Step 1: Configure Telegram Integration
Telegram offers the simplest setup. Open Telegram, search for @BotFather, and send /newbot. Name the bot and choose a username. BotFather returns an API token. Add it to OpenClaw's config file at ~/.config/openclaw/config.json:
{
"channels": {
"telegram": {
"token": "1234567890:AAHdqTcvCH1vGWJxfSeofSAs0K5PALDsaw",
"dmPolicy": "pairing"
}
}
}
Set dmPolicy to "pairing" for interactive approval or "allowlist" with specific chat IDs for automated workflows. Start the Gateway and send a message to your bot. OpenClaw will respond with a pairing code. Enter the code to link your account.
Step 2: Add Discord Bot
Visit Discord Developer Portal, create a new application, and navigate to the Bot section. Click "Add Bot" and copy the bot token. Enable "Message Content Intent" under Privileged Gateway Intents. Generate an OAuth2 invite URL with "bot" scope and "Send Messages," "Read Message History," and "Use Slash Commands" permissions. Add the bot to your server.
Update the OpenClaw config:
{
"channels": {
"telegram": { ... },
"discord": {
"token": "MTIzNDU2Nzg5MDEyMzQ1Njc4OQ.GhIjKl.MnOpQrStUvWxYz1234567890abcdefghijklmno",
"dmPolicy": "pairing",
"guildChannels": ["general", "dev-automation"]
}
}
}
The guildChannels array specifies which server channels OpenClaw will monitor. Restart the Gateway and test by sending a command in one of the configured channels.
Step 3: Integrate WhatsApp
OpenClaw supports two WhatsApp connection methods. For personal use, the wacli method is recommended. Install wacli via npm:
npm install -g @open-wa/wa-automateConfigure OpenClaw to use wacli:
{
"channels": {
"telegram": { ... },
"discord": { ... },
"whatsapp": {
"method": "wacli",
"sessionPath": "~/.config/openclaw/whatsapp-session"
}
}
}Launch the Gateway. On first run, wacli generates a QR code in the terminal. Scan it with WhatsApp on your phone (Settings → Linked Devices → Link a Device). Once paired, OpenClaw can receive and send WhatsApp messages. For production deployments requiring higher message volumes, use the WhatsApp Business API method with Meta verification.
Step 4: Connect Slack Workspace
Create a Slack app at api.slack.com/apps. Enable Socket Mode and generate an App-Level Token with connections:write scope. Subscribe to message.channels and message.im events. Install the app to your workspace and copy the Bot User OAuth Token.
Add to OpenClaw config:
{
"channels": {
"telegram": { ... },
"discord": { ... },
"whatsapp": { ... },
"slack": {
"botToken": "xoxb-1234567890123-4567890123456-abcdefghijklmnopqrstuvwx",
"appToken": "xapp-1-A0123456789-4567890123456-abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ",
"socketMode": true
}
}
}
Restart the Gateway. Invite the bot to channels with /invite @YourBot. Test with a direct message or channel mention.
Step 5: Unified Command Handlers
With multiple platforms configured, create cross-platform command handlers. OpenClaw provides a skill system for defining reusable automation tasks. Create a skill file at ~/.config/openclaw/skills/deploy.js:
module.exports = {
name: 'deploy',
description: 'Deploy application to staging or production',
handler: async (args, context) => {
const { platform, userId } = context;
const environment = args[0] || 'staging';
// Execute deployment script
const result = await context.exec(`~/scripts/deploy.sh ${environment}`);
return `Deployment to ${environment} completed. Platform: ${platform}`;
}
};This skill works identically across Telegram, Discord, WhatsApp, and Slack. Send "deploy production" from any platform and OpenClaw executes the script, returning the same response format to each channel.
Access Control and Security
Multi-platform environments require robust access control. OpenClaw supports platform-specific policies. Configure allowlists per platform:
{
"channels": {
"telegram": {
"token": "...",
"dmPolicy": "allowlist",
"allowedUsers": ["123456789", "987654321"]
},
"discord": {
"token": "...",
"dmPolicy": "allowlist",
"allowedUsers": ["1234567890123456789"]
}
},
"execApprovals": {
"autoApprove": ["/Users/mac/scripts/deploy.sh", "/Users/mac/scripts/build.sh"],
"requireApproval": ["*"]
}
}
The allowedUsers array restricts access to specific user IDs. The execApprovals section defines which shell commands auto-execute and which require manual approval. For production systems, keep requireApproval: ["*"] to prevent arbitrary code execution.
Real-World Use Cases
Teams use multi-platform OpenClaw for various automation scenarios:
- iOS CI/CD: Trigger Xcode builds from Slack, Telegram, or Discord. OpenClaw runs Fastlane on the remote Mac and streams logs to all platforms. Developers choose their preferred interface without changing the pipeline.
- Server monitoring: Configure cron jobs to check server health and send alerts to WhatsApp for on-call engineers and Slack for the ops channel. Single automation script, multiple notification channels.
- Cross-team collaboration: Product managers use WhatsApp to request feature flags. OpenClaw updates config files on the remote Mac and notifies the dev team via Discord. No need for everyone to use the same platform.
- Emergency response: Security teams receive vulnerability alerts on Signal (encrypted) and trigger remediation scripts. OpenClaw logs all actions and posts summaries to Slack audit channels.
Performance Considerations
Running multiple platform connectors increases Gateway resource usage. On a VNCMac M4 16GB Mac mini, the Gateway with Telegram, Discord, WhatsApp, and Slack consumes approximately 200-300 MB RAM and negligible CPU when idle. During active message processing, CPU usage spikes briefly (1-5%) per command execution. Network bandwidth is minimal: each platform uses WebSocket or long polling with keepalive packets every 30-60 seconds.
For high-traffic environments (100+ messages per hour across all platforms), monitor the Gateway process. OpenClaw handles concurrent messages by queuing them and processing sequentially. If latency becomes an issue, scale horizontally by running separate Gateway instances per platform and using a shared Redis backend for state synchronization.
Troubleshooting Common Issues
If a platform fails to connect, check the following:
- Invalid tokens: Verify bot tokens haven't expired. Telegram tokens are permanent, but Discord and Slack tokens can be regenerated, invalidating old ones.
- Network blocking: Ensure HTTPS (443) is allowed. Some corporate VPNs block WebSocket connections needed for Discord and Slack.
- Message Content Intent (Discord): Without enabling this privileged intent, the bot won't receive message content, only events.
- WhatsApp session expiry: wacli sessions last 14 days of inactivity. If OpenClaw stops receiving WhatsApp messages, re-scan the QR code to refresh the session.
- Slack Socket Mode: If Socket Mode isn't enabled, events won't reach the Gateway. Check app configuration in api.slack.com.
Enable debug logging in OpenClaw config ("logLevel": "debug") to see detailed platform connection status and message routing. Logs appear in ~/.config/openclaw/logs/gateway.log.
Advanced Configuration: Platform-Specific Features
Each platform supports unique features that OpenClaw can leverage:
- Discord Rich Embeds: Send structured responses with fields, thumbnails, and color coding. Use OpenClaw's
context.sendmethod with Discord-specific embed objects. - Telegram Inline Keyboards: Add interactive buttons to messages. Create approval workflows where users click "Approve" or "Deny" instead of typing commands.
- Slack Interactive Components: Use block kit for forms and interactive messages. Collect input data before executing automation tasks.
- WhatsApp Media Messages: Trigger automation from photos or documents. OpenClaw can download media, process it with system tools, and respond with results.
Cost Analysis: Platform-Specific Pricing
Most platforms offer free tiers suitable for OpenClaw automation:
- Telegram: Completely free with no message limits or API fees.
- Discord: Free for bots. No usage-based charges. Rate limits apply but are generous for automation.
- WhatsApp wacli: Free using personal WhatsApp account. WhatsApp Business API charges per conversation (pricing varies by region).
- Slack: Free tier supports Socket Mode and unlimited message history for apps. Paid workspaces may enforce app installation policies.
- Signal: Completely free and open-source. No commercial API, but signal-cli works for automation.
The primary cost is the remote Mac infrastructure. A VNCMac M4 16GB instance runs all platforms simultaneously with room for build processes and other automation tasks. Total monthly cost is predictable and independent of message volume, unlike serverless platforms that charge per invocation.
Summary
Configuring OpenClaw with multiple messaging platforms creates a flexible, unified automation system. Teams communicate using their preferred tools while benefiting from centralized AI-powered workflows. A remote Mac from VNCMac provides the stable, persistent environment needed to run the Gateway 24/7 with full macOS accessibility APIs. This approach eliminates platform lock-in, reduces automation fragmentation, and allows teams to scale communication without rewriting automation logic.