LINE #

Connect your own LINE Official Account so your LINE conversations flow into the app and an AI Agent can reply. You connect by pasting your LINE Messaging API credentials (Channel secret + access token) and setting one webhook URL — no coding required.

What Is the LINE Integration? #

The LINE integration links a LINE Official Account (OA) you own to the platform using LINE’s official Messaging API — LINE’s own system for sending and receiving messages automatically, instead of you typing them by hand in the LINE app. Your 1-to-1 chats with people who have added your OA as a friend become available inside the app, and an AI Agent, Broadcasts, and a shared inbox work on top of them.

Unlike Telegram or WhatsApp Web, this is an official integration — it uses LINE’s own Messaging API, so it’s stable and within LINE’s rules. Because LINE has no one-click “connect” button for third-party tools, you paste your OA’s credentials once during setup.

Availability. LINE Official Accounts are most common in Japan, Taiwan, Thailand, and Indonesia, and are not available in the EU. You need a LINE Official Account registered in a supported region to use this channel.

Before You Start #

You’ll create (or use) three things in LINE’s own consoles. This is a one-time setup of about 5 minutes.

1. A LINE Official Account (created in the LINE Official Account Manager). If you don’t have one yet, log in with your LINE Business ID and create a new account — give it a name and fill in the short form.
2. A Messaging API channel for that OA. The easiest way is to enable it from inside the OA Manager (see Step 1 below) — you don’t have to create the channel by hand in the Developers Console first. When prompted, pick an existing provider or create a new one.
3. From that channel, three values you’ll paste into the app:
   • Channel ID (Basic settings tab) — optional, informational only
   • Channel secret (Basic settings tab)
   • Channel access token — a long-lived token you issue on the Messaging API tab

No business documents are required for a standard (unverified) Official Account — just a LINE Business ID. Verification (the blue badge) is optional and only offered in some regions.

Setting Up LINE #

Step 1: Enable the Messaging API for Your Official Account #

1. Log in to the LINE Official Account Manager (or create a new Official Account first).
2. Open your OA.
3. Click Settings (top-right corner).
4. In the settings menu, click Messaging API.
5. The status starts as Disabled — click to enable it.
6. Choose the provider for this channel (the company/developer that owns it). If you don’t have one yet, create a new provider, then confirm.

Step 2: Get Your Credentials from the Developers Console #

Enabling the Messaging API creates a channel under your provider in the LINE Developers Console.

1. Open the developer account / provider.
2. Click into the Messaging API channel.
3. Open the Basic settings tab and copy your Channel ID and Channel secret.
4. Open the Messaging API tab, issue (or re-generate) a long-lived Channel access token, and copy it.

Keep these values handy — you’ll paste them into the app next.

Step 3: Connect LINE in the App #

1. In the left sidebar, click Settings near the bottom.
2. In the Settings left rail, under Channels, click Channels.
3. Find the LINE card and click Connect.
4. Optionally, paste your Channel ID — informational only.
5. Paste your Channel secret.
6. Paste your Channel access token.
7. Click Connect.
8. The app validates the credentials with LINE and shows “Connected to: <your OA name>”. If the credentials are wrong, you’ll get an error — re-issue the access token in the LINE Developers Console and try again.

Step 4: Set the Webhook URL in LINE #

After connecting, the app shows a Finish setup in LINE section with a webhook URL — copy it. (A webhook URL is just a web address; pasting it into LINE tells LINE where to automatically send new messages.) Then in the LINE Developers Console for your Messaging API channel:

1. Open the Messaging API tab.
2. Paste the URL into Webhook URL.
3. Click Update.
4. Turn Use webhook ON.

Step 5: Fix the Official Account Manager Settings (Important) #

By default, a LINE OA handles chats and auto-replies itself, which stops messages from reaching the AI. Back in the LINE Official Account Manager, open your OA settings and set:

If the app warns that your account is in Chat mode, switch it to Bot mode here — the bot can’t receive or send until you do.

Step 6: Test the Bot #

1. From a different phone (e.g. your own LINE app), add your Official Account as a friend and send it a message.
2. Open the app and go to Chats — the incoming message appears in the conversation list.
3. If an AI Agent is handling this channel, you’ll see it reply automatically to the test message.

Once connected with the webhook set and the toggles above correct, your LINE account shows as Connected on the Channels page and the AI responds to incoming messages.

Cost #

LINE is a free channel in the app — there’s no per-message charge and no monthly connection fee from us. Note that LINE’s own plans have their own monthly limits on push messages (proactive sends), which vary by region and account type. Replies sent shortly after a customer messages you are free on LINE; proactive/broadcast sends count against your LINE plan’s quota.

Media Messages #

Incoming photos, videos, voice notes, files, stickers, and locations are recognized so the AI knows media was sent (a short note is added to the conversation). Outbound AI replies are text and images in this version. Long replies are automatically trimmed to LINE’s 5,000-character limit.

Session Management #

Checking Connection Status #

Your LINE connection status is shown on the LINE card on the Channels page:

The card also re-checks your account’s Chat mode setting every time you open the Channels page. If your LINE account has been switched back to Chat mode (which stops the bot from receiving or sending), an amber warning appears on the card telling you to switch it back to Bot mode in the LINE Official Account Manager — re-check the Step 5 toggles there and the warning clears on the next visit.

Disconnecting #

Open the LINE card and click Manage, then click Disconnect in the panel that opens and confirm Remove LINE?. This removes the connection on our side. To fully stop LINE from sending events, also turn Use webhook off (or delete the webhook URL) in the LINE Developers Console.

Limitations #

• One Official Account per connection. Connect each OA separately; an OA can only be linked to one account.
• Text + image sending. The AI replies with text and images; rich “Flex”/template/carousel messages are not sent in this version.
• Region. LINE Official Accounts aren’t available in the EU; you need an OA in a supported region (e.g. Japan, Taiwan, Thailand, Indonesia).
• Reply timing. LINE’s free instant replies have a short time window; messages sent later are delivered as (quota-counted) push messages automatically.

Troubleshooting #

Credentials Rejected When Connecting #

• Make sure you created a Messaging API channel (not “LINE Login”).
• Re-issue a long-lived channel access token on the Messaging API tab and paste the fresh value.
• Confirm you copied the Channel secret from the Basic settings tab (not the Channel ID).

Bot Not Replying #

• Confirm Webhooks is On in both the Developers Console and the OA Manager.
• Confirm the Webhook URL matches the one shown in the app.
• Confirm Response mode is Bot (not Chat) in the OA Manager.

Customer Gets Two Replies #

• Turn Auto-response messages and Greeting messages Off in the OA Manager — LINE’s built-in auto-replies are sending alongside the AI.

Messages Not Arriving in the App #

• Verify the contact has added your Official Account as a friend (LINE only delivers messages from friends).
• Re-check the webhook URL and that Use webhook is on.

Best Practices #

• Complete the OA Manager toggles (Bot mode, Webhooks on, Greeting + Auto-reply off) — most setup problems come from these.
• Reply promptly to keep replies within LINE’s free window and conserve your push quota.
• Keep your access token safe — anyone with it can send as your Official Account. Re-issue it in the Developers Console if it leaks.