Standalone webhook gateway for OpenAB — bridges Telegram and/or LINE to any running OAB instance via WebSocket. Deploy alongside an existing OpenAB service to enable Telegram and/or LINE support. At least one platform must be configured. Source: https://github.com/openabdev/openab

OpenAB Gateway is a standalone webhook bridge that connects Telegram and LINE to any running OpenAB instance via WebSocket.
Telegram ──POST──▶ ┌──────────────────┐
LINE ──POST──▶ │ OpenAB Gateway │ ◀──WebSocket── OAB Pod
│ :8080 │ (OAB connects out)
└──────────────────┘
Deploy this template alongside an existing OpenAB service (Claude, Cursor, Codex, etc.) to add Telegram and LINE support without redeploying OAB.
/newbot and follow the prompts123456:ABC-DEF...) → paste into Telegram Bot Token/setprivacy → Disable so the bot sees all group messagesFill in the tokens for the platform(s) you want to enable and click deploy. A public HTTPS domain is auto-assigned. You can enable Telegram only, LINE only, or both.
After deployment, register your gateway URL with Telegram (replace YOUR_TOKEN, YOUR_DOMAIN, and optionally YOUR_SECRET):
# Without webhook secret (simpler, less secure)
curl "https://api.telegram.org/botYOUR_TOKEN/setWebhook?url=https://YOUR_DOMAIN/webhook/telegram"
# With webhook secret (recommended — matches TELEGRAM_SECRET_TOKEN you set)
curl "https://api.telegram.org/botYOUR_TOKEN/setWebhook?url=https://YOUR_DOMAIN/webhook/telegram&secret_token=YOUR_SECRET"
Expected response: {"ok":true,"result":true,"description":"Webhook was set"}
In your OpenAB service (same Zeabur project), edit /home/agent/.config/openab/config.toml and add:
[gateway]
url = "ws://openab-gateway:8080/ws"
Then restart the OpenAB service. OAB connects outbound to the gateway — no inbound ports needed on OAB.
Internal hostname:
openab-gatewayresolves within the same Zeabur project via internal DNS. If your gateway service has a different name, use that name instead.
Send a message to your Telegram bot. The gateway receives it and forwards it to OAB via WebSocket. OAB processes it and replies through the gateway.
In LINE Developers Console → Messaging API tab:
https://YOUR_DOMAIN/webhook/lineIn config.toml, add platform = "line" to the gateway section:
[gateway]
url = "ws://openab-gateway:8080/ws"
platform = "line"
Restart the OpenAB service after saving.
| Path | Platform |
|---|---|
POST /webhook/telegram | Telegram |
POST /webhook/line | LINE |
GET /ws | OAB WebSocket (internal) |
GET /health | Health check |