f7d7148cf0
Source-grounded rewrite of 529 published docs pages with per-unit information-loss verification: 1,713 factual corrections cited to src/**, generated surfaces regenerated, frontmatter titles preserved for i18n, release notes pages untouched. All docs gates green. Closes #100141
3.8 KiB
summary, read_when, title
| summary | read_when | title | ||
|---|---|---|---|---|
| Zalo ClawBot channel setup through the external openclaw-zaloclawbot plugin |
|
Zalo ClawBot |
OpenClaw connects to Zalo ClawBot through the catalog-listed external @zalo-platforms/openclaw-zaloclawbot plugin. Login uses a Zalo Mini App QR code; the plugin id in config is openclaw-zaloclawbot.
Compatibility
| Plugin Version | OpenClaw Version | npm dist-tag | Status |
|---|---|---|---|
| 0.1.4 | >=2026.4.10 | latest |
Active / Beta |
Prerequisites
- Node.js >= 22
- OpenClaw installed (
openclawCLI available) - A Zalo account on a mobile device to scan the login QR code
Install with onboard (recommended)
openclaw onboard
Pick Zalo ClawBot from the channel menu. The wizard installs the plugin from the official catalog (integrity-verified), renders the login QR in the terminal, and finishes the channel once you scan it with the Zalo app.
Manual installation
To add the channel to an already-onboarded gateway:
1. Install the plugin
openclaw plugins install "@zalo-platforms/openclaw-zaloclawbot@0.1.4"
Use the exact pinned version so OpenClaw verifies the package against the catalog integrity hash during install.
2. Enable the plugin in config
openclaw config set plugins.entries.openclaw-zaloclawbot.enabled true
3. Generate a QR code and log in
openclaw channels login --channel openclaw-zaloclawbot
Scan the terminal-rendered QR code with the Zalo mobile app, accept the Terms of Use inside the Zalo Mini App, and authorize the session.
4. Restart the gateway
openclaw gateway restart
How it works
Unlike the standard Zalo channel, which requires registering your own Zalo Official Account (OA) and configuring static developer credentials, Zalo ClawBot is an owner-bound personal assistant on shared official infrastructure:
- Onboarding: the QR code resolves to a Zalo Mini App that binds a newly provisioned, private bot under a shared official OA directly to your Zalo user ID.
- Owner-bound privacy: the bot only communicates with its owner. Messages from other users are dropped at the platform level.
- Official API path: the plugin uses Zalo Bot Platform APIs, not browser or web-session automation.
Under the hood
The plugin communicates with Zalo via a persistent long-polling loop (getUpdates). Webhooks are disabled by default for local desktop/terminal gateway runs. Messages are processed client-side and mapped to your local agent runtime.
The plugin manages bot credentials under the OpenClaw state directory. Treat that directory as sensitive and cover it under the same access-control and backup policy as the rest of OpenClaw state.
This plugin's runtime lives entirely in the external @zalo-platforms/openclaw-zaloclawbot package; behavior details below beyond install/config are as reported by the plugin's maintainers and are not verified against OpenClaw core source.
Troubleshooting
- QR login timeout: the login token (
zbsk) expires after 5 minutes for security. If the QR code expires before you scan it, rerun the login command to generate a new one. - Gateway fails to load: confirm your OpenClaw host version is
2026.4.10or higher. Older versions do not support the external npm-plugin installation ledger this ID requires.
Related
- Channels Overview - all supported channels
- Zalo - the bundled Zalo Bot Creator / Marketplace channel
- Pairing - DM authentication and pairing flow
- Plugins - installing and managing plugins