Neura Market Logo

Zalo ClawBot Channel Setup via openclaw-zaloclawbot Plugin

This page explains how to connect OpenClaw to Zalo ClawBot using the external openclaw-zaloclawbot plugin. It covers installation, configuration, and QR code login for developers setting up a Zalo channel.

Read this when

  • You want a personal Zalo assistant bot with QR-code login
  • You are installing or troubleshooting the openclaw-zaloclawbot channel plugin

OpenClaw connects to Zalo ClawBot using the external @zalo-platforms/openclaw-zaloclawbot plugin listed in the catalog. Login relies on a Zalo Mini App QR code; the plugin id in the config is openclaw-zaloclawbot.

Compatibility

Plugin VersionOpenClaw Versionnpm dist-tagStatus
0.1.4>=2026.4.10latestActive / Beta

Prerequisites

  • Node.js >= 22
  • OpenClaw installed (openclaw CLI available)
  • A Zalo account on a mobile device to scan the login QR code

Install with onboard (recommended)

openclaw onboard

Choose Zalo ClawBot from the channel menu. The wizard pulls the plugin from the official catalog (integrity-verified), shows the login QR in the terminal, and completes the channel once you scan it with the Zalo app.

Manual installation

To attach the channel to a gateway that is already onboarded:

1. Install the plugin

openclaw plugins install "@zalo-platforms/openclaw-zaloclawbot@0.1.4"

Use the exact pinned version so OpenClaw checks the package against the catalog integrity hash during installation.

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 QR code shown in the terminal 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 setting up static developer credentials, Zalo ClawBot acts as an owner-bound personal assistant on shared official infrastructure:

  1. Onboarding: the QR code points to a Zalo Mini App that binds a newly provisioned, private bot under a shared official OA directly to your Zalo user ID.
  2. Owner-bound privacy: the bot only talks to its owner. Messages from other users are discarded at the platform level.
  3. Official API path: the plugin uses Zalo Bot Platform APIs, not browser or web-session automation.

Under the hood

The plugin talks to Zalo through a persistent long-polling loop (getUpdates). Webhooks are turned off by default for local desktop or terminal gateway runs. Messages are processed client-side and mapped to your local agent runtime.

The plugin stores bot credentials under the OpenClaw state directory. Treat that directory as sensitive and protect 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 install and config are as reported by the plugin's maintainers and have not been 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, run the login command again to generate a new one.
  • Gateway fails to load: confirm your OpenClaw host version is 2026.4.10 or higher. Older versions do not support the external npm-plugin installation ledger that this ID requires.
  • Channels Overview - all supported channels
  • Zalo - the bundled Zalo Bot Creator / Marketplace channel
  • Pairing - DM authentication and pairing flow
  • Plugins - installing and managing plugins