Skip to main content
Connecting LINE to Cura is different from Meta channels: instead of a login pop-up, you copy three credentials out of LINE and paste Cura’s webhook URL back into LINE. Because of that, most LINE problems are a LINE-side switch in the wrong position, not a Cura bug — and Cura can’t flip those switches for you. LINE’s settings are split across two consoles, which is the single biggest source of confusion:
  • LINE Official Account Manager (manager.line.biz) — your business settings: Response mode, greeting messages, auto-replies.
  • LINE Developers Console (developers.line.biz) — your technical settings: Channel ID / Secret / Access Token, the webhook URL, and Use webhook.
Each section below is one symptom an owner actually sees. We label whether the fix is on LINE’s side (you change a setting in one of those consoles) or Cura’s side.

​
LINE connected, but no messages reach Cura

What you see: Cura shows the LINE channel as connected, but the Inbox stays empty — test messages you send to your Official Account never appear. Why it happens: For LINE to deliver messages to Cura, three switches on LINE’s side must all be on. If any one is off, LINE quietly keeps the messages and Cura never hears about them. This is a LINE setting, not a Cura fault — so the fix is on LINE’s side.
1

Set Response mode to Bot (LINE Official Account Manager)

Open LINE Official Account Manager → Settings → Response settings. Set Response mode to Bot.If the account is in Chat mode, LINE handles conversations manually and the webhook to Cura is switched off — so Cura receives nothing.
Since late 2022, LINE lets Chat and webhook run together, so keeping human chat available no longer breaks the bot on its own. The setting that actually silences Cura is the webhook being off (next steps), or the built-in auto-responders taking over (see the next section).
2

Turn on Use webhook (LINE Developers Console)

Open LINE Developers Console → your provider → your Messaging API channel → Messaging API tab. Turn the Use webhook toggle ON. If it’s off, LINE never sends events to Cura no matter what else is set.
3

Confirm Cura's webhook URL is pasted in

On that same Messaging API tab, the Webhook URL must be the exact URL Cura shows for this inbox (it looks like https://…/webhooks/line/<your-inbox-id>). You’ll find it in Cura under Integrations → Channels → open the LINE inbox. Copy it from Cura, paste it into LINE, and click Update, then Verify.
Send a test message to your Official Account from another phone — it should now land in the Cura Inbox within a few seconds.
Fastest way to test: open your Official Account’s Add friend QR code (in LINE OA Manager), add it from a second phone, and send “hello”. If it reaches Cura, the pipe is working.

​
Customers get a canned LINE reply as well as Cura’s answer

What you see: A customer messages your LINE Official Account and gets two replies — Cura’s AI answer plus a generic LINE greeting or auto-reply — or gets the canned LINE reply instead of Cura’s. Why it happens: LINE Official Accounts ship with built-in auto-responders turned on: a Greeting message (sent when someone adds you) and Auto-reply / keyword response messages. These fire from LINE directly, in parallel with Cura. LINE’s own docs recommend turning them off when a Messaging API bot is handling replies — “especially if this is the first time creating a LINE Bot.” The fix is on LINE’s side.
1

Disable the greeting message

In LINE Official Account Manager → Settings → Response settings, set Greeting message to Disabled (or turn off the toggle). Cura doesn’t need it — you can build a welcome into your AI instructions instead.
2

Disable auto-response / keyword replies

In the same Response settings, turn off Auto-response messages (also shown as Response message or Keyword response). If your account has AI response messages / an AI chatbot feature enabled, turn that off too — it competes with Cura.
Message your Official Account again. You should now get only Cura’s reply, once.
Leave Webhooks ON while you disable these. The goal is “webhook on, auto-responders off” — not turning everything off, which would stop Cura receiving too.

​
The connection won’t complete — you can’t find the right credentials

What you see: The Cura connect wizard asks for a Channel ID, Channel Secret, and Channel Access Token, and you’re not sure where each one lives — or you paste values and the connection is rejected. Why it happens: LINE keeps these in two different places, and it’s easy to grab the wrong value (for example, pasting the Basic ID @xxxxxxx where the numeric Channel ID belongs). The fix is to copy each from the right screen.
1

Channel ID and Channel Secret — Basic settings

In LINE Developers Console → your Messaging API channel → Basic settings, copy the Channel ID (a number like 1234567890) and the Channel Secret. Paste each into the matching field in Cura.
Cura uses the Channel Secret to check that inbound webhooks genuinely come from LINE. If the Secret is wrong or mistyped, LINE will connect but Cura will reject the events as unverified — so double-check this value if messages don’t arrive.
2

Channel Access Token — Messaging API tab

Switch to the Messaging API tab of the same channel, scroll to Channel access token (long-lived), and click Issue. Copy the token and paste it into Cura’s Channel Access Token field.
Use the long-lived token, not a short-lived one. Keep the token and secret private — treat them like a password.
3

Finish and grab your webhook URL

Complete the wizard. Cura creates the inbox and shows a webhook URL — copy it and paste it back into LINE (see the first section), then enable Use webhook.
Once the credentials save and the webhook is on, a test message reaches the Cura Inbox.

​
The webhook URL won’t verify

What you see: You paste Cura’s webhook URL into LINE, click Verify, and LINE shows an error instead of Success. Why it happens: LINE requires the endpoint to be HTTPS with a valid, browser-trusted certificate (self-signed certificates are rejected). Cura’s endpoint already meets this — you never manage a certificate — so a failed verify almost always means the URL itself is wrong, not a security problem on Cura’s side.
1

Re-copy the exact URL from Cura

Go back to Integrations → Channels → the LINE inbox in Cura and copy the webhook URL again, in full. A missing character or a stray space at the end is the usual cause. Paste it into LINE’s Webhook URL field and click Update.
2

Check the inbox is still active

If you deleted or archived the LINE inbox in Cura, its webhook URL stops responding and Verify will fail. Make sure the inbox still exists in Cura before verifying. See A channel shows as disconnected.
Click Verify — LINE should now show Success. (Verify only tests the endpoint; you still need Use webhook ON for messages to flow.)
A one-off Verify failure with the URL correct is usually transient — wait a moment and try again. If it keeps failing on a URL you copied straight from Cura, contact support@cura.so.

​
LINE says “You have reached your monthly limit”

What you see: LINE reports a monthly message limit reached, and some outbound messages from Cura fail. Why it happens: This is a LINE plan limit, by design — not something Cura can raise. But it matters far less than it sounds, because of how LINE bills messages:
  • Reply messages are free and do not count toward your quota.
  • Only push messages (and broadcasts) count.
Cura always tries to answer with a free reply first, and only falls back to a paid push if LINE’s short reply window has already closed by the time the AI responds. So in normal back-and-forth conversation, Cura barely touches your quota. You’d typically only hit the limit if you also send broadcasts from LINE OA Manager, or if replies are frequently delayed past the reply window.
1

Check what's consuming the quota

In LINE Official Account Manager, review your plan’s monthly message usage. On the free (Communication) plan, the push/broadcast allowance is small — 500 messages/month in Thailand at the time of writing. Broadcasts you send yourself count against the same pool.
2

Raise the limit on LINE's side, if you need to

If you genuinely send enough push/broadcast messages to need more, upgrade the LINE plan (Light / Standard) in LINE Official Account Manager. This is a LINE billing change and is separate from your Cura subscription.
Reply-only conversations keep working even at the cap — the limit only blocks push/broadcast sends.
Cura watches your LINE quota for you and alerts your workspace when usage crosses ~80%, so a cap rarely arrives as a surprise.

​
Good to know

  • No 24-hour window. Unlike WhatsApp, LINE lets you reply to a customer any time after they’ve added your Official Account — there’s no closing window. See Messaging windows by channel.
  • Grey-shield (unverified) accounts work fully with Cura. You don’t need a verified (blue-shield) LINE account to connect or reply. Verification is a discoverability/trust step you can do later; it isn’t a Cura prerequisite.