This document was written by AI and has been manually reviewed.
Drivers Overview
A driver is the adapter between NextBridge and a specific chat platform. Each driver handles receiving messages from its platform and sending messages to it.
Supported platforms
| Platform | Driver | Receive | Send | Notes |
|---|---|---|---|---|
| Tencent QQ | ✅ | ✅ | Supports multiple protocol backends (NapCat, Lagrange, OneBot v11) | |
| Discord | Discord | ✅ | ✅ | Receive via bot gateway; send via webhook or bot |
| Telegram | Telegram | ✅ | ✅ | Uses long polling |
| Feishu / Lark | Feishu | ✅ | ✅ | Webhook receive; IM API send |
| DingTalk | DingTalk | ✅ | ✅ | Webhook receive; Robot API send |
| Yunhu (云湖) | Yunhu | ✅ | ✅ | Webhook receive; open API send |
| KOOK (开黑啦) | KOOK | ✅ | ✅ | WebSocket receive; bot API send; uploads to KOOK CDN |
| VoceChat | VoceChat | ✅ | ✅ | |
| Matrix | Matrix | ✅ | ✅ | Client sync loop; E2E encryption supported when enable_e2e is enabled |
| Signal | Signal | ✅ | ✅ | Requires signal-cli REST API |
| Microsoft Teams | Teams | ✅ | ✅ | Bot Framework connector |
| Google Chat | Google Chat | ✅ | ✅ | REST API with service account |
| Slack | Slack | ✅ | ✅ | Socket Mode or Events API receive; bot or webhook send |
| Mattermost | Mattermost | ✅ | ✅ | WebSocket receive; REST API send |
| Rocket.Chat | Rocket.Chat | ✅ | ✅ | Outgoing webhook receive; REST API or incoming webhook send |
| Webhook | Webhook | ❌ | ✅ | Send-only generic HTTP webhook |
| ✅ | ✅ | Uses neonize (go-whatsapp bindings); no Node.js required |
How drivers work
Every driver:
- Registers a sender with the bridge on startup so the bridge can call it to deliver messages.
- Listens for incoming messages (WebSocket, long-polling, or HTTP webhook).
- Normalizes each incoming message into a
NormalizedMessageand passes it to the bridge. - Sends formatted text and attachments when the bridge calls its sender.
Media handling
All drivers share a common media-download utility. When a message with attachments arrives, the bridge passes the attachment list to the target driver's send() method. Each driver downloads the file (up to max_file_size bytes) and re-uploads it using the target platform's native API.
If a file exceeds the size limit or the download fails, a text fallback is appended to the message:
[Image: photo.jpg](https://example.com/photo.jpg)