OpenClaw LINE Bot: The Complete Setup Tutorial (2026)

The fastest way to connect OpenClaw to LINE is ZenClaw. MixerBox AI’s managed service deploys in 9 seconds and handles LINE through a shared @zenclawai Official Account plus a pairing code — you don’t register an Official Account, apply for a Messaging API channel, or configure a webhook URL. This post has two paths: ZenClaw managed (click through) and self-hosted OpenClaw (the full LINE Developers Console walk).

Quick pick: which path is for you

No code and no interest in webhooks or TLS? Go ZenClaw managed. Want your own LINE Official Account with end-to-end control? Go self-host. Side-by-side:

ZenClaw managed (recommended, 1 minute)

The ZenClaw path skips webhooks entirely. Users add the shared @zenclawai account as a friend, send a pairing code, and you’re connected. The flow is designed for non-technical users. Steps:

1. Sign in at zenclaw.ai
2. Click “Hire AI Employees Now” → dashboard → “Add New OpenClaw Installation”
3. Wait 9 seconds for the instance
4. In the Channels section, pick LINE
5. The UI shows: Add @zenclawai as a friend → click “Generate pairing code”
6. Copy the code, send it to @zenclawai in LINE
7. Paired. Chatting with @zenclawai is now the same as chatting with your AI employee

One LINE account can only bind to one instance at a time, so unbind before switching. Invite @zenclawai into a new LINE group and each group becomes its own session.

Self-hosted OpenClaw on LINE: the full flow

Self-hosting is 6 big steps: LINE Official Account → Messaging API channel → grab tokens → paste into OpenClaw → set webhook URL → live test. This assumes you already have OpenClaw running (see OpenClaw complete beginner’s guide). LINE’s official docs are at developers.line.biz/en/docs/messaging-api.

Step 1: Create a LINE Official Account

Go to manager.line.biz (LINE Official Account Manager), sign in, and click “Create account”. Fill in name, category, upload avatar and cover. You’ll end up with an @xxxxxxxx ID — that’s the public account users add as a friend.

Step 2: Create a Messaging API channel

Go to developers.line.biz (LINE Developers Console) and sign in with the same LINE account.

1. Create a Provider (team or company name)
2. Under the provider click Create a Messaging API channel
3. Link the channel to the Official Account from Step 1 (pick it from the list)
4. Fill in name, description, category, icon. Create.

Step 3: Grab the Channel Secret and Channel Access Token

• In the channel’s Basic settings: find Channel Secret and copy it
• Switch to Messaging API: scroll to Channel access token (long-lived), click Issue, and copy the token

Copy the token the second it’s issued. It reappears on page reload, but don’t lose it.

Step 4: Configure it in OpenClaw

Edit ~/.openclaw/openclaw.json (or use the OpenClaw dashboard). Under channels.line, set:

{
  "channels": {
    "line": {
      "channelSecret": "your Channel Secret",
      "channelAccessToken": "your Channel Access Token"
    }
  }
}

Restart the gateway (default port 18789). Official config docs: docs.openclaw.ai/cli/config.

Step 5: Set the webhook URL

Back in LINE Developers → Messaging API page:

1. Webhook URL: paste your OpenClaw HTTPS URL, for example https://your-domain/line/webhook
2. Click Verify to test reachability
3. Check Use webhook
4. Turn off Auto-reply messages and Greeting messages (both will swallow traffic)

The webhook URL must be HTTPS with a valid cert. Use Let’s Encrypt or a Cloudflare tunnel.

Step 6: Live test

Scan the QR on the Messaging API page → add as friend → send a message → check OpenClaw’s gateway log. OpenClaw writes sessions to ~/.openclaw/sessions/line/.

Common gotchas

Most people get stuck on: webhook URL isn’t HTTPS, cert expired, Use webhook wasn’t checked, Auto-reply not disabled, or token copied wrong. Walkthrough:

• Webhook verification fails → Confirm URL is reachable and TLS is valid (curl https://your-domain/line/webhook)
• No messages coming through → Check Use webhook is on and Auto-reply is off
• Token verification fails → Re-issue the Channel Access Token, watch for stray whitespace
• Bot receives but doesn’t reply → OpenClaw model or skill isn’t configured, check the log
• ~/.openclaw/ loses settings on restart → Docker volume isn’t mounted, see OpenClaw Docker volume settings lost fix

ZenClaw managed sidesteps all of these.

Further reading

• OpenClaw Complete Beginner’s Guide for Non-Technical Users
• Self-hosted OpenClaw vs ZenClaw: Cost Comparison
• E-commerce AI Employee Playbook
• OpenClaw Telegram Group Privacy Mode Fix