OpenClaw Messenger

Standalone OpenClaw channel plugin for Facebook Page Messenger direct messages. Users can talk to the configured OpenClaw assistant through Messenger; replies are sent back through the Meta Graph API.

Proof of concept

The channel has been tested in a live Messenger conversation with the dedicated OpenClaw Facebook Page. The screenshot shows messages sent to the Page and the assistant's reply delivered back in Messenger.

This repository is intentionally chat-only. Product-specific generation, payments, quotas, subscriptions, tenant provisioning, and application logic are outside its scope.

Channel

The plugin registers one channel in OpenClaw as Facebook (Page Messenger). The canonical channel id is facebook; messenger, fb, and fbm are compatibility aliases and do not create separate channels.

The integration handles Meta webhook verification, request signatures, deduplication, sender authorization, pairing, direct-message routing, supported attachments, and channel-neutral actions rendered as Messenger quick replies.

Install and configure

npm install
npm run build
npm test
npm pack
openclaw plugins install ./dj-shortcut-facebook-*.tgz
openclaw channels list --all

Configure channels.facebook in OpenClaw and set the Meta callback URL to https://<gateway-host>/facebook/webhook. Never commit Page tokens, app secrets, verify tokens, PSIDs, or live deployment configuration.

Development

Requirements: Node.js 24+ and npm 11+.

npm run check
npm pack --dry-run

See docs/standalone-messenger.md for the scope, migration boundary, and channel-list acceptance check.

Automation

GitHub Actions runs the build, test suite, and package dry-run on pushes to main and on pull requests. Dependabot checks npm dependencies (including the OpenClaw peer/build dependency) and GitHub Actions weekly.

ClawHub publishing is available through the manually started Publish to ClawHub workflow. Add a CLAWHUB_TOKEN repository secret, protect the clawhub-release environment if approval is required, and start the workflow with a version matching package.json. It defaults to a dry-run; disable that input only for an intentional release.