OpenClaw on WhatsApp: Your AI Agent Where 2 Billion People Already Live
You don't need a new app. WhatsApp is already on your phone, already trusted by everyone you know. Here's how to run a self-hosted AI agent there — cron alerts, file analysis, smart replies — without touching a cloud dashboard.
There's a quiet shift happening in how developers think about AI interfaces. For a while, the dominant paradigm was the chat app — build a custom frontend, point it at an API, ship. But increasingly, the question being asked on Hacker News and developer forums is: why build a new interface at all? WhatsApp already has 2 billion monthly active users. It's already on every phone. It already has end-to-end encryption baked in.
What if your AI agent lived there?
OpenClaw natively supports Telegram as its primary mobile channel — and it's excellent. But many people don't have Telegram. Their business contacts, family, team — they're on WhatsApp. Running your AI agent through WhatsApp means it's already in the same thread as your real conversations. No context switch. No extra app.
Get the weekly AI agent digest 🦞
What's shipping in AI tools, every Monday. No fluff.
This guide shows you exactly how to do it using wacli — an open-source WhatsApp CLI that integrates cleanly with OpenClaw's automation layer — and when WhatsApp makes sense vs. Telegram for your specific workflow.
Why WhatsApp, Not Another Bot Platform
Most WhatsApp AI solutions fall into two camps: clunky business API integrations that cost $0.01 per message and require a Meta Business account approval process, or jailbroken ChatGPT wrappers that disappear when OpenAI updates their ToS.
Neither is what builders actually want. What builders want is: my agent, on my server, messaging me through the app I already use.
The key insight is that WhatsApp automation via wacli is outbound — your OpenClaw agent sends messages to you (or others) from your existing WhatsApp account. It's the same as if you typed it yourself. No business API. No per-message fee. No approval wait.
This makes it perfect for a specific set of use cases:
Cron alerts
Your agent messages you a morning brief, portfolio summary, or server alert — directly in WhatsApp.
Forwarding digests
Agent scans email, GitHub, or RSS and sends you a WhatsApp summary when something important happens.
File delivery
Agent generates a report, converts it to PDF, and sends it to you or a contact via WhatsApp.
Group notifications
Send automated updates to a WhatsApp group — client updates, team alerts, release notes.
What the Community Is Saying
The conversation is happening everywhere this week. Here's the pattern emerging from three corners of the developer internet:
The thread turned into a meta-discussion about AI agents and their interfaces. Top comment: "The next big thing won't be a new AI chat app — it'll be AI agents that live inside the communication tools people already have. WhatsApp, iMessage, SMS. The interface that wins is the one that requires no behaviour change." (347 upvotes)
Multiple threads from builders showing off self-hosted WhatsApp bots. The most-liked framing: "Forget the AI app race. The real play is embedding your agent into WhatsApp. That's where decisions get made, where clients are, where your team already works. A 2-second WhatsApp message beats a 30-second app context switch every time."
Builders sharing setups that run AI agents as WhatsApp contacts. Common pattern: one WhatsApp number linked to a local LLM via a CLI bridge, available 24/7 for family and team without them needing to install anything. The friction reduction is dramatic — especially for non-technical household members.
How OpenClaw + WhatsApp Works
The integration uses wacli — a Go-based CLI tool that connects to WhatsApp via the multi-device API (the same protocol WhatsApp Web uses). It authenticates with your personal WhatsApp account via QR code, stores a local session, and exposes a simple command-line interface for sending messages and searching history.
OpenClaw then uses this as a tool in its automation layer. Specifically:
- Outbound sending — OpenClaw calls
wacli send textto deliver messages to any contact or group - File delivery —
wacli send filefor PDFs, images, reports - History search —
wacli messages searchfor context retrieval from past conversations - Cron integration — scheduled jobs that fire alerts and digests at configured intervals
The agent doesn't "receive" WhatsApp messages in an interactive loop — that would require the Business API or unofficial hooks. This is about outbound delivery: your OpenClaw agent proactively messages you through WhatsApp as part of its automation runs.
Note on interactive use
If you want a fully interactive AI agent that responds to WhatsApp messages you send it (two-way chat), that requires a more complex setup with WhatsApp Business API or an unofficial webhook bridge. For most developers, the outbound automation pattern covered here is enough — and much simpler. For two-way interactive use, Telegram is the better choice.
Step-by-Step Setup
Step 1: Install wacli
Install via Homebrew (macOS/Linux) or Go:
# Homebrew (recommended)
brew install steipete/tap/wacli
# Or via Go
go install github.com/steipete/wacli/cmd/wacli@latest
Step 2: Authenticate with WhatsApp
This links wacli to your existing WhatsApp account — no new number needed:
wacli auth
# Scan the QR code with your phone
# WhatsApp → Settings → Linked Devices → Link a Device
# Session stored at ~/.wacli
Your phone needs to be online for initial auth, but wacli uses WhatsApp's multi-device protocol — it stays connected even when your phone is offline after the first sync.
Step 3: Run initial sync
wacli sync --follow
# Syncs your chat list and recent messages
# Leave running for a minute, then Ctrl+C
# Verify it's working:
wacli chats list --limit 10
wacli doctor
Step 4: Find your contact JIDs
Every WhatsApp contact has a JID (Jabber ID) — you need this to send messages:
# Search by name or number
wacli chats list --query "John"
# Direct chats: <number>@s.whatsapp.net
# Groups: <id>@g.us
# Or use phone number directly
wacli send text --to "+14155551212" --message "Test from wacli"
Step 5: Tell OpenClaw to use it
In your OpenClaw session, Kade (or your agent) can now call wacli directly. Store your own number in MEMORY.md or TOOLS.md for easy reference:
# In TOOLS.md or MEMORY.md:
WhatsApp: My number: +351XXXXXXXXX
WhatsApp: Team group JID: 1234567890-123456789@g.us
Cron Alerts via WhatsApp
The most powerful pattern: combine OpenClaw's cron scheduler with wacli to deliver proactive WhatsApp alerts on any schedule.
Here's a cron job that sends a morning market brief to your WhatsApp every weekday at 8am:
// OpenClaw cron job config
{
"name": "WhatsApp Morning Brief",
"schedule": {
"kind": "cron",
"expr": "0 8 * * 1-5",
"tz": "Europe/Belgrade"
}
"payload": {
"kind": "agentTurn",
"message": "Pull BTC/ETH prices, top crypto news, and any urgent GitHub alerts. Format as a concise morning brief and send to my WhatsApp: wacli send text --to '+351XXXXXXXXX' --message '[brief here]'."
}
"sessionTarget": "isolated"
}
The agent spins up in an isolated session, does the research, composes the brief, and fires the WhatsApp message — all without you touching anything. By the time you reach for your phone in the morning, the brief is already there.
6 Real Automation Recipes
Daily crypto portfolio alert
Schedule: 0 8 * * *
Agent fetches portfolio data, calculates 24h P&L, and sends a WhatsApp summary. If any position moves more than 5%, adds an alert emoji.
GitHub PR digest
Schedule: 0 9 * * 1-5
Lists open PRs across your repos, formats as a quick WhatsApp message. No more opening GitHub to check — it comes to you.
Weekly investor update to group
Schedule: 0 17 * * 5
Agent compiles the week's metrics, writes a concise investor update, sends to your WhatsApp investor group. No manual copy-paste.
Server health check
Schedule: */30 * * * *
Pings your critical endpoints every 30 minutes. If anything is down, immediately fires a WhatsApp alert with the affected service and error.
PDF report delivery
Schedule: 0 7 * * 1
Agent generates a Monday morning business report as a PDF (analytics, revenue, tasks) and sends the file directly to your WhatsApp.
Client follow-up reminder
Schedule: at: specific ISO timestamp
Schedule a one-shot reminder to message a specific contact. Agent drafts the follow-up text based on past conversation context and sends it at the right time.
Privacy & Security Considerations
WhatsApp uses end-to-end encryption for message content — but there are important nuances when running automation:
What's private
- —Message content is E2E encrypted
- —wacli stores session locally (~/.wacli)
- —No third-party API involved (no Meta Business fee)
- —Your messages never leave your server
What to be aware of
- —Meta sees metadata (who you talk to, when)
- —Your WhatsApp account is linked — don't abuse it (no spam)
- —Keep ~/.wacli directory permissions tight (chmod 700)
- —Don't send sensitive data (keys, passwords) via WhatsApp messages
# Lock down your wacli session directory
chmod 700 ~/.wacli
# Verify health regularly
wacli doctor
WhatsApp vs. Telegram for OpenClaw
Both are excellent. The choice depends on what you're optimizing for:
| Feature | Telegram | |
|---|---|---|
| Interactive AI chat | ❌ Outbound only (native) | ✅ Full two-way chat |
| Setup complexity | 🟡 Medium (QR auth + wacli) | ✅ Simple (bot token) |
| User adoption | ✅ 2B users — they already have it | 🟡 800M — tech-savvy crowd |
| File delivery | ✅ Supported via wacli send file | ✅ Supported natively |
| Group messaging | ✅ Supported (group JID) | ✅ Supported natively |
| Privacy | 🟡 E2E but Meta metadata | ✅ No Meta dependency |
| Cron alerts | ✅ Yes, via wacli in job | ✅ Yes, native delivery |
| Best for | Proactive alerts to non-tech contacts | Interactive personal agent sessions |
The smart move: use both. Run your interactive OpenClaw sessions on Telegram (full two-way, full bot setup here), and use WhatsApp for outbound alerts and delivering updates to contacts or groups who don't have Telegram.
Get Started Today
The entire setup — install, auth, first message — takes about 10 minutes. Here's the shortest path:
# 1. Install
brew install steipete/tap/wacli
# 2. Authenticate (scan QR with phone)
wacli auth
# 3. Initial sync
wacli sync --follow
# 4. Send your first message
wacli send text --to "+YOURNUMBER" --message "OpenClaw WhatsApp is live 🦞"
# 5. Set up a cron job in OpenClaw to automate delivery
# /cron add — then configure schedule + agentTurn payload
Once it's running, you'll wonder how you were manually checking things before. Your agent handles the monitoring — you just get the message.
Pair this with OpenClaw's cron system for scheduling, context management for long-running tasks, and automation workflows for the full playbook.
The interface layer shouldn't require a behaviour change. Your agent should come to where you already are. With wacli + OpenClaw, now it does.
Related Articles
Telegram Bot Setup for OpenClaw
The full guide to setting up interactive two-way AI chat via Telegram.
OpenClaw Cron Jobs
Schedule your agent to act autonomously — morning briefs, alerts, reports.
Automation Workflows
10 real automation recipes that run themselves, with full configs.
Get the AI Adaptation Playbook
12 pages. 5 frameworks. 6 copy-paste workflows. Everything you need to future-proof your career with AI.
Instant delivery · No spam · Unsubscribe anytime