> ## Documentation Index
> Fetch the complete documentation index at: https://www.voiceflow.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect a Voiceflow agent to LINE

> Connect LINE to a Voiceflow text agent. Configure the platform, host the relay, test replies and prepare release.

## Overview

Answer one-to-one messages to a LINE Official Account with a Voiceflow agent. You run an HTTPS relay that verifies LINE events and uses each incoming event’s reply token to answer.

<a id="before-you-begin"></a>

## Before you begin

Collect the agent, account and host access.

| Requirement | Obtain before installation |
| --- | --- |
| Voiceflow owner | An existing agent with a known support answer, a private project API key, project ID and reviewed Environment alias. [Build the agent](/docs/documentation/build/overview) first, then [publish the intended release](/docs/documentation/deploy/environments/publishing). |
| Official Account | A LINE Official Account with Messaging API enabled and access to its provider and channel in LINE Developers. |
| Credentials | The Messaging API channel secret, a channel access token and the bot’s user ID; keep them together for the same channel. |
| Relay operator | A Node.js host, public HTTPS hostname, private secrets and persistent disk; an operator who can investigate paused conversations. |

The example provides public-policy text support. Keep private Voiceflow and platform credentials on the host; a customer’s messaging identity does not authorize access to orders or account records. Have the agent return text only and provide a support route in its instructions. Buttons, audio and Handoff traces need additional adapters; see [Adapt agent replies](/docs/guides/channels/messaging/adapt-agent-replies).

<a id="create-platform-app"></a>

## Prepare the platform account

Create the exact app or account this relay will use.

### 1. Enable the Messaging API

Create a LINE Official Account in [Official Account Manager](https://manager.line.biz/). In its settings, enable **Messaging API** and select or create the owning provider. Open the resulting Messaging API channel in [LINE Developers](https://developers.line.biz/console/). Channel creation starts from Official Account Manager; it is not a new channel button in the developer console.

### 2. Obtain channel credentials

Copy the channel secret from **Basic settings**. Issue an appropriate channel access token from its Messaging API settings; LINE recommends a token with a specified expiration for managed deployments. Put it in `LINE_ACCESS_TOKEN` and plan renewal before expiration. Read the bot user ID using the following request and set `LINE_BOT_USER_ID` to `userId`:

```js
// identity.mjs — node --env-file=.env identity.mjs
import { request } from './core.mjs';
console.log(await request('https://api.line.me/v2/bot/info', {
  method: 'GET', headers: { Authorization: `Bearer ${process.env.LINE_ACCESS_TOKEN}` }
}));
```

Keep the account out of group chats for this private-support recipe. Review the Official Account’s regional plan and sending quotas before launch. See [Build a bot](https://developers.line.biz/en/docs/messaging-api/building-bot/).

<a id="run-relay"></a>

## Run the relay

Configure and host the supplied executable example.

Use the [configuration file](/docs/examples/messaging/line.env.example) for this platform. Every name below is read by the supplied artifact; IDs identify the resources prepared above. `VF_ENVIRONMENT` is the Environment alias, not a version label pasted from another project.

```dotenv
VF_API_KEY=YOUR_PRIVATE_VOICEFLOW_PROJECT_KEY
VF_PROJECT_ID=YOUR_VOICEFLOW_PROJECT_ID
VF_ENVIRONMENT=YOUR_ENVIRONMENT_ALIAS
DATA_DIR=/var/lib/voiceflow-messaging
PORT=8080
PLATFORM=line
LINE_ACCESS_TOKEN=YOUR_CHANNEL_ACCESS_TOKEN
LINE_CHANNEL_SECRET=YOUR_CHANNEL_SECRET
LINE_BOT_USER_ID=YOUR_LINE_BOT_USER_ID
```

### 1. Download and configure the relay

On a Linux host you administer, create `/opt/voiceflow-messaging` and extract the [relay archive](/docs/examples/messaging/messaging-relay.zip) there. Use Node.js 22.12 or later. Run `node --test fixtures.test.mjs` first: it generates signed synthetic events and mocks all remote calls, without credentials or live messages. Save the configuration above as `.env`, replacing every `YOUR_` value; restrict it to the service account with `chmod 600 .env`. Set `DATA_DIR` to a private persistent directory that this account can write.

The archive includes `core.mjs`, platform adapters, HTTP/Teams entry points, local fixture tests and a package manifest. Run `node --env-file=.env relay.mjs serve`. The HTTP relay uses only Node built-ins; it does not need `npm install`.

### 2. Expose the HTTPS endpoint

Point your own DNS hostname to the host. Terminate HTTPS with a valid public certificate and proxy to `127.0.0.1:8080`. For example, with [Caddy](https://caddyserver.com/docs/quick-starts/reverse-proxy) installed:

```sh
caddy reverse-proxy --from support.example.com --to 127.0.0.1:8080
```

Replace the example hostname, allow inbound 80/443 for certificate provisioning and keep the relay port private. Use a separate hostname and credentials for testing. Confirm `https://YOUR_HOST/health` returns `ok` before registering `/webhook`.

### 3. Keep one process running

After the foreground check, stop it and create a service using the unit below. Keep one process and one writable data directory per installation. Do not run this file store on ephemeral serverless storage or start multiple replicas.

```ini
# /etc/systemd/system/voiceflow-messaging.service
[Unit]
Description=Voiceflow messaging relay
After=network-online.target

[Service]
User=relay
WorkingDirectory=/opt/voiceflow-messaging
ExecStart=/usr/bin/node --env-file=.env relay.mjs serve
Restart=on-failure
UMask=0077

[Install]
WantedBy=multi-user.target
```

Create the non-login `relay` service user, give it read access to the application and `.env`, and ownership of `/var/lib/voiceflow-messaging`. Confirm `/usr/bin/node --version` is 22.12 or later, or substitute your actual Node path. Then run `sudo systemctl daemon-reload` and `sudo systemctl enable --now voiceflow-messaging`. Expect the service to stay active; keep the HTTPS proxy running through its own service.

The file store is a small single-process starting point. Back it up privately and monitor disk space, queue age and failures. Higher traffic needs a transactional inbox/outbox and per-conversation workers before adding replicas. Session keys and customer text are stored in the data directory; apply your retention and access policy there as well as in Voiceflow.

<a id="register-events"></a>

## Register incoming events

Connect the platform to your hosted endpoint.

### 1. Save and verify the LINE callback

In the channel’s **Messaging API** tab, edit **Webhook URL** to `https://YOUR_HOST/webhook`, choose **Update**, then **Verify**. Expect **Success**, including for LINE’s verification request containing an empty `events` array. Enable **Use webhook** and **Webhook redelivery**.

### 2. Enable delivery and check the signature

In Official Account Manager, disable competing automatic replies or greetings when they would duplicate your agent’s response. The relay verifies `X-Line-Signature` as base64 HMAC-SHA256 of the raw body with the channel secret. Do not parse and reserialize JSON before signature verification. See [Receiving messages](https://developers.line.biz/en/docs/messaging-api/receiving-messages/).

<a id="conversation-routing"></a>

## Route conversations and replies

Keep the customer, agent session and reply destination aligned.

| Stage | Mapping in the example |
| --- | --- |
| Customer identity | `destination` bot user ID + `source.userId`; only `source.type: user` is accepted. |
| Incoming text | Text message events with their `replyToken` and `webhookEventId`. |
| Visible reply | One POST to `https://api.line.me/v2/bot/message/reply`, containing up to five text messages under the same one-use token. |
| Duplicate | Deduplicate `webhookEventId`; redeliveries can arrive out of order and retain the original event identity. |

The relay hashes platform, destination account, customer/thread, project and Environment into a bounded Voiceflow `userID`. It creates a session with the private project key, stores the returned `sessionKey`, launches once, then sends `{ action: { type: "text", payload: text } }` to `/v4/interact`. Text traces become platform replies. Follow-ups reuse the key; starting a session every message would reset the conversation.

[Reply tokens](https://developers.line.biz/en/reference/messaging-api/#send-reply-message) are single-use and should be consumed promptly; use within one minute is required, with additional limits on old redelivered events. The sample uses the earlier of 45 seconds after receipt and just under 20 minutes after the event’s original timestamp. It rejects an expired event before running the agent and never retries with a different token. Keep the agent’s first reply fast enough for session creation, launch and text execution to finish within it.

The adapter packs 4000-character chunks into one request, failing if it would need more than five messages. It does not fall back to billable push messaging. Stickers, images and other inputs receive a text-only notice. Unsend/deletion handling and group conversations require further implementation before enabling those use cases.

<a id="test-conversation"></a>

## Test a customer conversation

Verify the reply in the destination you installed.

### 1. Send a real platform message

Scan the Official Account’s QR code from the channel’s Messaging API tab, add it as a friend and send your prepared text question. Expect one answer in the same chat.

### 2. Check continuity and isolation

Ask a related follow-up, then test with a second authorized customer. Confirm the intended Voiceflow project and exchange in [Transcripts](/docs/documentation/measure/transcripts). Run `node --env-file=.env relay.mjs inspect` while the service is stopped to compare event IDs, conversation keys and completion states without printing session tokens.

### 3. Check this platform’s delivery behavior

Use a short agent response to check the reply-token deadline. Redeliver the same signed test event: the agent must not run again or consume its token twice.

A saved callback, accepted API request or successful Voiceflow Run does not prove this platform conversation. Keep local signed-fixture tests separate from this authenticated customer test.

<a id="troubleshooting" />

### The callback saves but no reply arrives

Check platform access as well as endpoint connectivity.

A successful webhook verification checks connectivity only. For no answer, inspect token age, token reuse, access-token validity, response length and whether another responder consumed the token. Do not retry an uncertain one-use reply blindly.

### A conversation is paused or a reply is duplicated

Reconcile remote effects before resuming the saved job.

Inspect the event’s `phase`, `failedDuring`, saved traces and accepted chunks in the private data file. A runtime timeout can occur after a tool action; a send timeout can occur after the platform accepted the message. The sample pauses that conversation and does not retry either effect automatically. Follow [Recover failed messages](/docs/guides/channels/messaging/recover-failed-messages), then repeat the platform test.

<a id="go-live"></a>

## Release and maintain the connection

Promote the tested route and keep recovery available.

### 1. Approve the production destination

Check the account’s availability, plan and quotas, remove competing auto-responses, then test from an authorized customer account. Run one instance of the relay with enough capacity to meet reply-token deadlines.

### 2. Release the reviewed agent

Have the Voiceflow owner publish the tested agent to the intended Environment. Deploy that alias and production credentials to the relay, restart its service and repeat the [customer test](#test-conversation) with a fresh customer/session. Existing session keys are not an automatic migration to a new release. Keep the previous deployment and state backup available for rollback.

### Rotate, update or disconnect

Maintain both the provider registration and the relay state.

Stop the service before changing `.env` or running maintenance commands. Rotate the platform credentials using its administrator controls, update the secret file and restart. If a webhook secret changes, update both sides and check a real event. For a release change, drain or reconcile pending jobs first; do not erase the state file to resolve a delivery problem.

To disconnect, disable/remove this callback or uninstall this app in the provider, stop the relay and revoke its unused credentials. Confirm no new events arrive and retain/delete customer state according to your policy. Keep the registration details needed to reconnect. See [Pause automated replies](/docs/guides/channels/messaging/pause-automated-replies) for a temporary conversation-specific pause.
