ADP Channel

ADP-OpenClaw demo channel plugin with Go WebSocket backend.

The ADP Channel plugin is a demo-grade channel integration that connects OpenClaw to the ADP platform via a Go-based WebSocket backend. ADP (likely referring to an internal or specialized communication platform) uses WebSocket connections for real-time bidirectional messaging, and this plugin implements the bridge between that protocol and OpenClaw's channel system. The architecture features a Go WebSocket server that maintains persistent connections with ADP clients, translating messages between the ADP protocol and OpenClaw's message format. Incoming ADP messages are forwarded to the OpenClaw gateway for AI processing, and responses are pushed back through the WebSocket connection in real-time. This Go backend approach is notable among OpenClaw plugins, which are typically written in TypeScript/JavaScript. Despite being described as a 'demo' plugin, it has surprisingly high adoption with over 10,700 weekly downloads — one of the highest in the entire plugin ecosystem. This likely indicates it's being used as a reference implementation or template for custom WebSocket-based channel integrations, or that the ADP platform has a larger user base than its sparse documentation suggests. The plugin is at version 0.0.69 (pre-1.0) and is maintained by @fomenyesu. Best suited for developers building custom WebSocket channel integrations who want a working reference implementation, or for users of the ADP platform who need OpenClaw connectivity. Not recommended as a production channel without thorough testing — the 'demo' label and pre-1.0 version suggest it's not fully hardened.

Tags: channel, websocket

Use Cases

Reference implementation for building custom WebSocket channel plugins
Real-time AI assistant for the ADP communication platform
Template for bridging Go-based backends with OpenClaw's Node.js plugin system
Demo/proof-of-concept for WebSocket-based channel integrations

Tips

Use this plugin as a reference implementation if you're building your own WebSocket-based channel integration
Study the Go WebSocket backend code to understand how to bridge non-JavaScript platforms with OpenClaw
If using in production, add reconnection logic and health checks to the WebSocket connection
Run the Go backend and OpenClaw gateway on the same host or local network to minimize WebSocket latency
Consider writing a pure TypeScript/JavaScript replacement if you want to avoid the Go runtime dependency

Known Issues & Gotchas

The 'demo' label means this plugin may lack error handling, reconnection logic, and edge case coverage found in production plugins
You need both Go and Node.js runtimes — the WebSocket backend runs in Go while the plugin itself is npm-installed
Version 0.0.69 means the API surface may change significantly before 1.0
High download count (10K+/week) may be inflated by CI/CD pipelines or dependency chains rather than actual usage
WebSocket security advisory (GHSA-rqpp-rjj8-7wv8) highlighted connection auth issues in OpenClaw — ensure your WebSocket connections are properly authenticated
No built-in rate limiting — implement your own if connecting to a high-traffic ADP deployment

Alternatives

WebSocket Plugin (native)
Paperclip Gateway Adapter
Custom Channel Extension

Community Feedback

ADP-OpenClaw demo channel plugin with Go WebSocket backend — a reference implementation showing how to bridge external WebSocket-based platforms with OpenClaw.
— npm

Channel plugins extend OpenClaw with new communication platforms. The WebSocket pattern used by ADP demonstrates real-time bidirectional messaging integration.
— OpenClaw Docs

OpenClaw serves HTTP and WebSocket protocols simultaneously on a single port, routing multiple channel methods. Plugins like ADP leverage this for real-time communication.
— dev.to

Frequently Asked Questions

What is ADP in this context?

ADP refers to a specific communication platform that uses WebSocket connections for real-time messaging. The plugin bridges this platform with OpenClaw. It's not related to the ADP payroll/HR company — it appears to be a specialized or regional messaging system.

Why does a 'demo' plugin have 10,000+ weekly downloads?

The high download count likely reflects use as a reference implementation for custom WebSocket integrations, inclusion in CI/CD build pipelines, or a larger-than-expected ADP platform user base. The 'demo' label refers to maturity level, not popularity.

Do I need Go installed to use this plugin?

Yes. The plugin includes a Go-based WebSocket backend that bridges ADP connections with OpenClaw. You need both Go (for the WebSocket server) and Node.js (for the OpenClaw plugin) installed on your system.

Can I use this as a template for my own WebSocket channel?

Yes, that's one of its best use cases. The plugin demonstrates the full pattern: Go WebSocket server → message translation → OpenClaw channel protocol. Study the code to understand how to bridge any WebSocket-based platform with OpenClaw.

Is this plugin safe for production use?

Use with caution. The 'demo' label and pre-1.0 version (0.0.69) suggest it may lack production hardening like robust error handling, reconnection logic, and comprehensive security measures. Test thoroughly and add your own safeguards.

Why use Go for the WebSocket backend instead of JavaScript?

Go excels at handling concurrent WebSocket connections with lower memory overhead than Node.js. For high-connection-count scenarios, the Go backend may perform better. However, it adds a runtime dependency that pure JS plugins avoid.

Configuration Examples

Basic ADP WebSocket connection

channels:
  adp:
    enabled: true
    websocketUrl: ws://localhost:9000
    apiKey: YOUR_ADP_API_KEY

ADP with custom Go backend

channels:
  adp:
    enabled: true
    websocketUrl: ws://adp-backend.internal:9000
    apiKey: YOUR_ADP_API_KEY
    reconnectIntervalMs: 5000
    healthCheckIntervalMs: 30000

Installation

openclaw plugins install adp-openclaw