OpenAB LINE Bundle

One-click OpenAB deployment for LINE — bot agent + webhook gateway bundled together. Fill in your LINE channel credentials and paste one webhook URL into the LINE Developers Console.

LINE ──POST──▶ ┌──────────────────┐ ◀──WebSocket── ┌────────────┐
               │  openab-gateway  │                │   openab   │
               │  (line only)     │                │  (Kiro CLI) │
               └──────────────────┘                └────────────┘
                  public HTTPS                       internal only

What's deployed

Service	Purpose	Public
openab	OAB agent running Kiro CLI	No
openab-gateway	LINE webhook → WebSocket bridge	Yes (auto HTTPS)

No PVC sharing, no manual config.toml edits. The agent's config.toml is generated on first boot with the gateway URL pre-wired to ws://openab-gateway:8080/ws and platform = "line".

Setup

1. Create a LINE Official Account + Channel

1. Go to LINE Official Account Manager → create a new account (or use an existing one).
2. Settings → Messaging API → Enable Messaging API → follow the prompts (you may need to create / pick a LINE Developers provider).
3. Open LINE Developers Console → your provider → your channel.
4. Basic settings tab → scroll to Channel secret → copy → paste into LINE Channel Secret.
5. Messaging API tab → scroll to Channel access token → click Issue → copy the long-lived token → paste into LINE Channel Access Token.
6. While in Messaging API tab, set:
   • Auto-reply messages: OFF (so LINE doesn't pre-empt your bot)
   • Greeting messages: optional, your call

2. (Optional) Get a Kiro API Key

If you have a paid Kiro subscription, go to kiro.dev → Settings → API Keys → create a key and paste it into KIRO_API_KEY. Free tier users skip this and authenticate post-deploy in step 4.

3. Deploy

Click deploy. A public HTTPS domain is auto-assigned to the gateway service.

4. Authenticate Kiro via Device Flow (free tier only)

Skip if you set KIRO_API_KEY in step 2.

After the openab service is running, open its terminal in Zeabur Dashboard and run:

runuser -u agent -- kiro-cli login --use-device-flow

Follow the URL and code to authorize in your browser.

5. Register the LINE Webhook URL

LINE has no programmatic setWebhook API — you must paste the URL into LINE Developers Console once.

1. Open the openab-gateway service page in Zeabur Dashboard → look at the auto-assigned domain (e.g. https://your-gateway.zeabur.app).
2. The full webhook URL is: https://<YOUR_GATEWAY_DOMAIN>/webhook/line
3. Go to LINE Developers Console → your channel → Messaging API tab.
4. Webhook URL → Edit → paste the URL → Update.
5. Use webhook → toggle ON.
6. Click Verify — you should see ✅ Success.

The openab-gateway service Instructions section shows the exact webhook URL pre-filled with your domain.

6. Test

Open the LINE app, scan the QR code from your channel's Messaging API page, add the bot as a friend, and send a message. The gateway receives it, forwards it to OAB via WebSocket, and OAB replies through the gateway.

Group chats: LINE bots can be invited to group chats. Behavior depends on your channel's settings under LINE Official Account Manager → Response settings.

Customization

• /home/agent/.config/openab/config.toml — OAB config (sessions, reactions, etc.). Created on first boot from a built-in template with the [gateway] block pre-wired. To regenerate, delete and restart.
• Image tags — bot tracks the floating stable channel (ghcr.io/openabdev/openab:stable) and auto-updates with each OpenAB stable release. Gateway is pinned at ghcr.io/openabdev/openab-gateway:0.5.1 (no :stable tag yet). To pin or bump, change the tag in Zeabur Dashboard → Service → Settings. Available tags: OpenAB / Gateway.
• Reply token caching — LINE reply tokens expire after ~1 minute. The gateway caches them and falls back to push API if expired or missing — no config needed.

Why no automatic webhook registration?

Unlike Telegram (which has a setWebhook API), LINE requires you to paste the webhook URL into the Developers Console and click Verify yourself — there's no server-to-server registration endpoint. This is a one-time setup; redeployments keep the same URL as long as the gateway domain is unchanged.

Want a different agent backend?

This bundle uses Kiro as the default agent. For Claude / Codex / Cursor / Gemini / OpenCode / Hermes / Grok, deploy the corresponding bot template separately together with the standalone OpenAB Gateway.

Want a different platform?

See OpenAB Telegram Bundle / Feishu Bundle or the standalone OpenAB Gateway for Google Chat, MS Teams, WeCom.

Links

• OpenAB GitHub
• LINE Setup Guide
• Standalone OpenAB Gateway Template