How to Connect OpenClaw to LINE

Prerequisites

• ✓A LINE Developers account with access to the LINE Developers Console at https://developers.line.biz/console/.
• ✓A Provider in the LINE Developers Console with a Messaging API channel you can configure.
• ✓An OpenClaw gateway reachable over HTTPS so LINE can call `https://gateway-host/line/webhook`.

Steps

1. 1

   Create a LINE Messaging API channel

   Start by creating the LINE side of the integration so you have credentials for OpenClaw. You do this in the LINE Developers Console under a Provider, where you add a Messaging API channel that represents your bot.

   textCopy

   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.

2. 2

   Collect the LINE channel access token and secret

   OpenClaw authenticates webhook calls from LINE using the channel access token and channel secret. Copy these values now; you will either paste them into your config or expose them via env vars or files.

   textCopy

   3.   Copy the **Channel access token** and **Channel secret** from the channel settings.

3. 3

   Enable and point the LINE webhook at your OpenClaw gateway

   LINE delivers all messages to your gateway via a webhook, so you must enable it and set the correct HTTPS URL. webhookPath` if you need a custom route.

   textCopy

   4.   Enable **Use webhook** in the Messaging API settings.
   5.   Set the webhook URL to your gateway endpoint (HTTPS required):
   
   https://gateway-host/line/webhook

4. 4

   Install or confirm the LINE plugin in OpenClaw

   Current OpenClaw releases bundle the LINE plugin, so you usually do not need a separate install. If you run an older build or a custom install that excludes LINE, install the plugin explicitly so the gateway exposes the LINE webhook.

   bashCopy

   openclaw plugins install @openclaw/line

5. 5

   Optionally install LINE from a local checkout

   If you are developing or customizing the LINE plugin, you can install it from a local path instead of the published package. This keeps your gateway using your checked-out plugin code while you iterate.

   bashCopy

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

6. 6

   Configure the LINE channel in your OpenClaw config

   Now wire your LINE credentials into OpenClaw so the gateway can verify signatures and send replies. The minimal config enables the channel, sets the access token and secret, and uses `dmPolicy: "pairing"` so new DM senders must be approved.

   jsonCopy

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

7. 7

   Use env vars or token files for LINE secrets

   For production you usually do not hardcode secrets in config. OpenClaw supports env vars for the default LINE account and also `tokenFile`/`secretFile` pointing at regular files, which avoids putting secrets directly in your config object.

   jsonCopy

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

8. 8

   Configure multiple LINE accounts if needed

   accounts`. Each account gets its own token, secret, and optional custom webhook path so you can route different LINE channels into the same gateway.

   jsonCopy

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

9. 9

   Control who can DM or use groups with LINE access policies

   By default, LINE DMs use pairing so unknown senders must be approved before messages reach your agent. *` access-control keys.

   bashCopy

   openclaw pairing list line
   openclaw pairing approve line <CODE>

10. 10

    Send rich LINE messages with channelData

    line` on your agent responses. The LINE plugin also exposes a `/card` command to send preset Flex messages directly from chat.

    jsonCopy

    {
      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",
          },
        },
      },
    }
    
    /card info "Welcome" "Thanks for joining!"

Configuration

Troubleshooting

Frequently asked questions