Apus connects to Zalo ClawBot through the catalog-listed external @zalo-platforms/apus-zaloclawbot plugin. Login uses a Zalo Mini App QR code; the plugin id in config is apus-zaloclawbot.

This plugin's runtime lives entirely in the external @zalo-platforms/apus-zaloclawbot package. Behavior details on this page beyond install and config are as reported by the plugin's maintainers and are not verified against Apus core source.

Compatibility

Plugin Version Apus Version npm dist-tag Status
0.1.4 >=2026.4.10 latest Active / Beta

Prerequisites

Install with onboard (recommended)

apus 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

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

Use the exact pinned version so Apus verifies the package against the catalog integrity hash during install.

2. Enable the plugin

apus plugins enable apus-zaloclawbot

Check the application result before logging in. Reinstallation preserves a plugin you explicitly disabled.

3. Generate a QR code and log in

apus channels login --channel apus-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. Verify the channel

apus channels status --probe

Start the Gateway if it is offline. Config changes follow hot reload. If the running channel has not picked up the saved login, run apus plugins reload apus-zaloclawbot, then check its status again.

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:

  1. 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.
  2. Owner-bound privacy: the bot only communicates with its owner. Messages from other users are dropped 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 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 Apus state directory. Treat that directory as sensitive and cover it under the same access-control and backup policy as the rest of Apus state.

Troubleshooting

Related