LINE

LINE connects to OpenClaw via the LINE Messaging API. The plugin runs as a webhook receiver on the gateway and uses your channel access token + channel secret for authentication.

Status: bundled plugin. Direct messages, group chats, media, locations, Flex messages, template messages, and quick replies are supported. Reactions and threads are not supported.

Bundled plugin

LINE ships as a bundled plugin in current OpenClaw releases, so normal packaged builds do not need a separate install.

If you are on an older build or a custom install that excludes LINE, install a current npm package when one is published:

bash
Copy
openclaw plugins install @openclaw/line

If npm reports the OpenClaw-owned package as deprecated or missing, use a current packaged OpenClaw build or a local checkout until the npm package train catches up.

Local checkout (when running from a git repo):

bash
Copy
openclaw plugins install ./path/to/local/line-plugin

Setup

1. Create a LINE Developers account and open the Console: https://developers.line.biz/console/
2. Create (or pick) a Provider and add a Messaging API channel.
3. Copy the Channel access token and Channel secret from the channel settings.
4. Enable Use webhook in the Messaging API settings.
5. Set the webhook URL to your gateway endpoint (HTTPS required):

text
Copy
https://gateway-host/line/webhook

The gateway responds to LINE’s webhook verification (GET) and inbound events (POST). If you need a custom path, set

or and update the URL accordingly.

Security note:

• LINE signature verification is body-dependent (HMAC over the raw body), so OpenClaw applies strict pre-auth body limits and timeout before verification.
• OpenClaw processes webhook events from the verified raw request bytes. Upstream middleware-transformed
  text

  Copy

  req.body
  values are ignored for signature-integrity safety.

Configure

Minimal config:

json5
Copy
{
  channels: {
    line: {
      enabled: true,
      channelAccessToken: "LINE_CHANNEL_ACCESS_TOKEN",
      channelSecret: "LINE_CHANNEL_SECRET",
      dmPolicy: "pairing",
    },
  },
}

Env vars (default account only):

• text

  Copy

  LINE_CHANNEL_ACCESS_TOKEN
• text

  Copy

  LINE_CHANNEL_SECRET

Token/secret files:

json5
Copy
{
  channels: {
    line: {
      tokenFile: "/path/to/line-token.txt",
      secretFile: "/path/to/line-secret.txt",
    },
  },
}

and must point to regular files. Symlinks are rejected.

Multiple accounts:

json5
Copy
{
  channels: {
    line: {
      accounts: {
        marketing: {
          channelAccessToken: "...",
          channelSecret: "...",
          webhookPath: "/line/marketing",
        },
      },
    },
  },
}

Access control

Direct messages default to pairing. Unknown senders get a pairing code and their messages are ignored until approved.

bash
Copy
openclaw pairing list line
openclaw pairing approve line <CODE>

Allowlists and policies:

• text

  Copy

  channels.line.dmPolicy
  :
  text

  Copy

  pairing | allowlist | open | disabled
• text

  Copy

  channels.line.allowFrom
  : allowlisted LINE user IDs for DMs
• text

  Copy

  channels.line.groupPolicy
  :
  text

  Copy

  allowlist | open | disabled
• text

  Copy

  channels.line.groupAllowFrom
  : allowlisted LINE user IDs for groups
• Per-group overrides:
  text

  Copy

  channels.line.groups.<groupId>.allowFrom
• Runtime note: if
  text

  Copy

  channels.line
  is completely missing, runtime falls back to
  text

  Copy

  groupPolicy="allowlist"
  for group checks (even if
  text

  Copy

  channels.defaults.groupPolicy
  is set).

LINE IDs are case-sensitive. Valid IDs look like:

• User:
  text

  Copy

  U
  + 32 hex chars
• Group:
  text

  Copy

  C
  + 32 hex chars
• Room:
  text

  Copy

  R
  + 32 hex chars

Message behavior

• Text is chunked at 5000 characters.
• Markdown formatting is stripped; code blocks and tables are converted into Flex cards when possible.
• Streaming responses are buffered; LINE receives full chunks with a loading animation while the agent works.
• Media downloads are capped by
  text

  Copy

  channels.line.mediaMaxMb
  (default 10).
• Inbound media is saved under
  text

  Copy

  ~/.openclaw/media/inbound/
  before it is passed to the agent, matching the shared media store used by other bundled channel plugins.

Channel data (rich messages)

Use

to send quick replies, locations, Flex cards, or template messages.

json5
Copy
{
  text: "Here you go",
  channelData: {
    line: {
      quickReplies: ["Status", "Help"],
      location: {
        title: "Office",
        address: "123 Main St",
        latitude: 35.681236,
        longitude: 139.767125,
      },
      flexMessage: {
        altText: "Status card",
        contents: {
          /* Flex payload */
        },
      },
      templateMessage: {
        type: "confirm",
        text: "Proceed?",
        confirmLabel: "Yes",
        confirmData: "yes",
        cancelLabel: "No",
        cancelData: "no",
      },
    },
  },
}

The LINE plugin also ships a

command for Flex message presets:

text
Copy
/card info "Welcome" "Thanks for joining!"

ACP support

LINE supports ACP (Agent Communication Protocol) conversation bindings:

• text

  Copy

  /acp spawn <agent> --bind here
  binds the current LINE chat to an ACP session without creating a child thread.
• Configured ACP bindings and active conversation-bound ACP sessions work on LINE like other conversation channels.

See ACP agents for details.

Outbound media

The LINE plugin supports sending images, videos, and audio files through the agent message tool. Media is sent via the LINE-specific delivery path with appropriate preview and tracking handling:

• Images: sent as LINE image messages with automatic preview generation.
• Videos: sent with explicit preview and content-type handling.
• Audio: sent as LINE audio messages.

Outbound media URLs must be public HTTPS URLs. OpenClaw validates the target hostname before handing the URL to LINE and rejects loopback, link-local, and private-network targets.

Generic media sends fall back to the existing image-only route when a LINE-specific path is not available.

Troubleshooting

• Webhook verification fails: ensure the webhook URL is HTTPS and the
  text

  Copy

  channelSecret
  matches the LINE console.
• No inbound events: confirm the webhook path matches
  text

  Copy

  channels.line.webhookPath
  and that the gateway is reachable from LINE.
• Media download errors: raise
  text

  Copy

  channels.line.mediaMaxMb
  if media exceeds the default limit.

Related

• Channels Overview — all supported channels
• Pairing — DM authentication and pairing flow
• Groups — group chat behavior and mention gating
• Channel Routing — session routing for messages
• Security — access model and hardening