Skip to main content
Kylon connects to LINE through a bring-your-own LINE Official Account. You provide the channel’s Channel Secret so Kylon can verify incoming webhooks. You can also provide a Channel Access Token if you want Kylon to register the webhook URL in LINE automatically and use LINE Messaging API features such as media downloads. Use this guide when you are setting up the LINE Official Account connection from an agent’s Connections page.
Kylon receives new webhook events after the connection is configured. LINE does not provide a general API for Kylon to backfill old chat history from before the webhook was enabled.

​
Before you start

You need:
  • Admin access to a LINE Official Account.
  • Access to the matching Messaging API channel in the LINE Developers Console.
  • A Kylon workspace channel where inbound LINE messages should be routed.
LINE’s own setup flow starts from a LINE Official Account. Per LINE’s Messaging API getting started guide, enabling the Messaging API for the official account creates the Messaging API channel.

​
Use an existing LINE Official Account

If your workspace already has a LINE Official Account, start here.
1

Open LINE Official Account Manager

Sign in to LINE Business ID and open the official account you want Kylon to receive messages from.LINE Business ID sign-in screen
2

Confirm the account

In LINE Official Account Manager, make sure you are working on the correct account.LINE Official Account Manager account list
3

Enable or open the Messaging API channel

If the Messaging API is not enabled for the account yet, enable it from LINE Official Account Manager. Then open the matching channel in the LINE Developers Console.LINE Developers Console showing a Messaging API channel card

​
Create a LINE Official Account

Skip this section if you already have the official account.
1

Create the official account

In LINE Official Account Manager, choose Create new and complete LINE’s required account form.LINE Official Account creation form
2

Enable the Messaging API

After the account is created, enable the Messaging API for it. LINE will create the corresponding Messaging API channel in the LINE Developers Console.

​
Create the Kylon connection

In Kylon, open the target agent, go to Connections, choose LINE Official Account, and enter: Do not paste the numeric Channel ID into either credential field.
The Channel Secret, Channel ID, and Channel Access Token are different values. A Channel Secret is commonly a 32-character value from Basic settings. A Channel ID is numeric. A Channel Access Token is an opaque token from the Messaging API tab and is usually much longer.
The Channel Access Token is not shown in LINE Official Account Manager. From the official account’s Messaging API settings, open the linked LINE Developers Console, select the same Messaging API channel by matching the Channel ID, then use the Messaging API tab to issue or copy a Channel Access Token.
After you submit the Kylon form, Kylon returns a webhook URL. If you did not provide a Channel Access Token, copy the webhook URL before closing the dialog.

​
Configure the LINE webhook

If you provided a Channel Access Token and Kylon reports that the LINE webhook was registered successfully, no manual URL paste is needed. In the LINE Developers Console, open the same Messaging API channel, go to the Messaging API tab, and confirm Use webhook is enabled. If you left the Channel Access Token blank, configure the webhook manually:
1

Paste the Kylon webhook URL

In Webhook settings, edit Webhook URL, paste the Kylon URL, and save it.LINE Developers Console webhook settings with Webhook URL, Verify, and Use webhook controls
2

Verify the webhook

Click Verify. LINE’s webhook URL verification sends a request with an empty events array. Kylon treats that signed empty-events request as a successful verification request.
3

Turn on Use webhook

Enable Use webhook. LINE’s bot setup guide requires the webhook URL to use HTTPS, verifies the endpoint, and then enables webhook delivery.
If Kylon should be the system handling incoming messages:
  • Turn off LINE’s automatic reply features in LINE Official Account Manager.
  • Keep webhook delivery on in the LINE Developers Console.
  • If the bot needs to operate in group or multi-person chats, enable Allow bot to join group chats in the LINE Developers Console’s Messaging API tab before inviting the account to the group. LINE’s group chat documentation notes that this setting is disabled by default.

​
What Kylon can receive

Kylon receives webhook events that LINE sends after the webhook is configured and enabled. Kylon does not receive:
  • Messages sent before the webhook was enabled.
  • Historical LINE chat history through a backfill API.
  • Manual reply activity that happens only inside LINE Official Account Manager.
For provider-level event shapes and Messaging API behavior, refer to LINE’s Messaging API reference.

​
Troubleshooting