LINE

ZeroClaw supports LINE via the Messaging API — receiving messages through an embedded webhook server and replying via the Reply API (with Push API fallback when the reply token has expired).

Prerequisites

1. A LINE Developers Console account.
2. A public HTTPS endpoint reachable from LINE's servers (or ngrok for local development).
3. ZeroClaw built with LINE channel support enabled (the channel-line feature on the zeroclaw-channels crate).

1. Create a LINE Bot

1. Log in to the LINE Developers Console.
2. Create a Provider (or use an existing one).
3. Create a new Messaging API channel under that Provider.
4. From the channel settings, collect two values:
   • Channel Access Token — Messaging API tab → Issue a long-lived token.
   • Channel Secret — Basic settings tab.

2. Configure ZeroClaw

Configure the LINE channel under [channels.line] with at minimum channel_access_token and channel_secret. See the Config reference for the full field index, defaults, and the dm_policy / group_policy enums (whose user-facing semantics are also covered in §6 below).

Using environment variables instead of config file

If you prefer not to store credentials in the config file, omit the token fields and export them as environment variables instead:

export LINE_CHANNEL_ACCESS_TOKEN="your-channel-access-token"
export LINE_CHANNEL_SECRET="your-channel-secret"

Environment variables take precedence over empty config fields.

3. Expose the Webhook Endpoint

LINE delivers messages by posting to your webhook URL. The embedded server listens on the configured webhook_port.

For local development (ngrok):

ngrok http 8443

Copy the https:// URL ngrok provides (e.g. https://abc123.ngrok.io).

For production: expose port 8443 (or the port you configured) behind an HTTPS reverse proxy (nginx, Caddy, etc.) or deploy directly on a server with a TLS certificate.

4. Register the Webhook in LINE Developers Console

1. Go to your channel → Messaging API tab → Webhook settings.
2. Set Webhook URL to https://your-domain.com/line/webhook.
3. Toggle Use webhook to on.
4. Click Verify — LINE will send a test request. ZeroClaw must be running for verification to succeed.

5. Start ZeroClaw

./target/release/zeroclaw --config zeroclaw.toml

Or via daemon mode:

zeroclaw daemon

Startup log signal:

LINE: webhook server listening on http://0.0.0.0:8443/line/webhook

6. Access Policies

DM (1:1 chat) — dm_policy

Pairing workflow:

1. ZeroClaw prints a pairing code in the log at startup.
2. The user opens a LINE DM with the bot and sends /bind <code>.
3. ZeroClaw confirms the pairing; subsequent DMs are accepted.

Group / multi-person chat — group_policy

7. Audio / Voice Message Transcription (optional)

When transcription is enabled (via the global [transcription] config — see Config reference), LINE audio message events are automatically downloaded from the LINE Content API and transcribed before being passed to the model.

The maximum accepted audio size is 25 MB. Larger files are silently skipped with a log warning.

8. Troubleshooting

Log keywords

See also

• Config reference — full config field index
• LINE Developers Documentation