Lobu’s WhatsApp adapter supports direct chats, group controls, and media-aware workflows. Under the hood, Lobu uses the WhatsApp Business Cloud API for message delivery and media handling.
C
Coding
online
List open PRs in lobu-ai/lobu12:01
Can't reach github.com — not in the agent's allowed domains.
Grant access?12:01
Allow for 1 hour12:01
Added github.com to allowed domains.
3 open PRs in lobu-ai/lobu:
• #214 Fix worker memory leak
• #219 Telegram adapter retries
• #223 Add Bedrock provider12:01
O
Ops Assistant
online
Summarize my active Linear sprint12:01
I need the `linear` skill to query Linear.
It bundles the Linear MCP and handles OAuth via Lobu.12:01
Go ahead12:01
Installed and connected.
Sprint "Week 15" (68% done):
• 11 merged, 3 in review, 2 todo
• Blocked: AUTH-234 (design)
• At risk: API-89 (due tomorrow)12:01
A
Assistant
online
Switch to Claude Sonnet12:01
You can change the model from your settings — opens a scoped page with your current agent config.12:01
Done — set to claude-sonnet-4-612:01
Now running on claude-sonnet-4-6 via OpenRouter.
Next messages will use the new model.12:01
- Obtain a WhatsApp Business access token, phone number ID, app secret, and verify token from the Meta Developer Portal.
- Run
lobu connections add whatsappto add the connection (prompts for the access token and phone number ID), or runlobu initto scaffold a new project and pick WhatsApp in the wizard. - Configure the webhook URL in the Meta Developer Portal to point to your gateway’s webhook endpoint.
- Start the stack with
lobu run -d— the bot starts handling messages on the configured phone number.
Configuration
Section titled “Configuration”| Field | Required | Type | Description |
|---|---|---|---|
accessToken | No | string | System User access token for WhatsApp Cloud API. |
phoneNumberId | No | string | WhatsApp Business phone number ID. |
appSecret | No | string | Meta App Secret for webhook HMAC-SHA256 signature verification. |
verifyToken | No | string | Verify token for webhook challenge-response. |
apiVersion | No | string | Meta Graph API version (default: v21.0). |
userName | No | string | Bot display name. |
Connection Settings
These settings apply to all platform connections and are passed in the settings object.
| Field | Required | Type | Description |
|---|---|---|---|
allowFrom | No | string[] | User IDs allowed to interact with this connection. Omit to allow all; empty array blocks all. |
allowGroups | No | boolean | Whether group messages are allowed (default true). |
userConfigScopes | No | string[] | Scopes that end users are allowed to customize. Empty = no restrictions. |
Features
Section titled “Features”- Cloud API integration via the WhatsApp Business Platform.
- Group controls with allow/deny behavior and optional mention requirement.
- Typing indicator status while responses are being generated.
- File/media support for inbound and outbound attachments.
- Conversation history window with configurable retention limits.
Typical Use Cases
Section titled “Typical Use Cases”- Personal assistant over WhatsApp chats.
- Group assistant that only responds when mentioned.
- Media-aware workflows (voice notes, files, images).