Run your LINE Official Account from the same inbox as Instagram.
LINE is the default messaging app in Japan, Taiwan and Thailand, which makes it the channel that decides whether a business in those markets is reachable at all. Most Western CRMs either ignore it or hand you a webhook and wish you luck. Inflowave treats a LINE Official Account the same way it treats an Instagram account: connect it once, and every inbound message becomes a conversation in the shared inbox with the full CRM record behind it - tags, pipeline stage, notes, assignment, history. Replies go back out from the same inbox, and so do push messages when the reply window has passed. The integration runs on the official LINE Messaging API. You connect by pasting the channel access token and channel secret from your own LINE Developers console, which means the Official Account stays yours - Inflowave never becomes the owner of the channel and you can disconnect without losing it. Every inbound message also fires the message_received workflow trigger, so the same automations you already run on Instagram and WhatsApp work on LINE without being rebuilt.
Create a Messaging API channel in the LINE Developers console (or open the one your Official Account already uses)
Copy the channel secret and issue a long-lived channel access token
In Inflowave, select the workspace the account belongs to - a LINE channel is always owned by one workspace, never shared across all of them
Open Settings, Connected Accounts, Add LINE, and paste the two values
Inflowave checks them against LINE before saving anything, so a wrong or expired token fails immediately rather than silently
Set the webhook URL shown on the confirmation screen in your LINE channel settings, and turn webhooks on
Agencies running Japanese or Thai clients alongside Western ones stop switching tools. LINE, Instagram, WhatsApp and Facebook threads sit in the same inbox with the same assignment rules.
Inbound LINE messages fire the same message_received trigger as every other channel, so existing qualification, tagging and routing workflows apply without a rebuild.
InfloAI can answer an inbound LINE message using the stored reply token, which is the cheapest way to send and keeps the conversation inside the window LINE gives you.
Messages from one-to-one chats, groups and rooms each become their own conversation thread rather than collapsing into one, so a group enquiry does not overwrite a private one.
Yes. Inflowave connects to an Official Account you own through its Messaging API channel. If you do not have one yet, create it in the LINE Official Account Manager first, then create the Messaging API channel in the LINE Developers console.
Two values from your Messaging API channel: the channel secret and a channel access token. Inflowave calls LINE to confirm which bot they belong to before storing anything, so a mistyped or expired value is rejected at the point of connection rather than turning into silent message failures later.
You do. Inflowave holds credentials you issued and can revoke. Disconnecting in Inflowave does not touch the account, the followers, or anything else in the LINE console.
A LINE channel belongs to exactly one workspace. That is deliberate. An unassigned channel would be visible and sendable from every workspace in the agency, which is how one client ends up messaging another client's followers. The connect call refuses rather than leaving it ambiguous.
Yes. Connect one Official Account per workspace. Each one has its own credentials, its own conversations and its own access rules, and staff only see the workspaces they are assigned to.
Every webhook carries an X-Line-Signature header. LINE gives each Official Account its own channel secret, so Inflowave first identifies which connected channel the event claims to be for, then verifies the signature against that channel's secret. An event that fails verification is discarded.
LINE lets you answer an inbound message for free using a short-lived reply token. Inflowave stores that token against the conversation so whoever answers - a person in the inbox or InfloAI - can use it. Once it expires, the message goes out as a push message instead, which counts against your LINE message quota.
Yes, LINE messages sit in the same message budget as Instagram, Facebook, WhatsApp and SMS. Your LINE push quota is separate and set by LINE on your Official Account plan; Inflowave can read your current quota consumption from LINE.
Only to users who have added your Official Account as a friend, and only as a push message. LINE has no equivalent of a cold outbound message to a stranger, and Inflowave will not pretend otherwise.
Inbound non-text messages create the conversation and the message row so the thread is complete, and the media itself is retrievable from LINE for a limited retention window. Text is what appears as the inbox preview line.
Yes. Inbound LINE messages create the same conversation records as any other channel, so InfloAI answers with the same brand voice and the same rules you configured for Instagram.
message_received, the same trigger Instagram, Facebook and WhatsApp use. It is fired after the message and reply token are safely stored, so a workflow never runs against a half-written conversation.
The LINE integration plugs into the same Inflowave workflow engine that handles DM automation, lead pipelines, and unified inbox. Connect a LINE Official Account to Inflowave. Inbound messages become CRM conversations, replies and pushes send from the shared inbox, and workflows fire on every message. Once connected, every event LINE fires can trigger an Inflowave automation - and every Inflowave action can write data back into LINE - so the two tools stay in sync without manual exports or copy-paste.
Most teams using Inflowave alongside LINE land on a similar setup pattern: connect the account on the integrations page, pick the events you want to react to, and route the data into the Inflowave entity it should live on (lead, contact, conversation, or pipeline stage). Setup takes about 12 minutes for a fresh workspace and is reversible - disconnecting cleanly removes the webhook and stops the data sync.
Inflowave's role is to be the CRM agencies run their clients on - which means the LINE integration's value lands hardest when there's a real conversation flow to attach data to. Agencies running multiple client workspaces use LINE per-client; a single business tends to wire one LINE account to all of its connected channels. Both shapes are supported by the same integration code path.
If LINE isn't the right fit, Inflowave ships native equivalents for many common workflows (built-in scheduling, built-in CRM, built-in unified inbox), so the integration is meant for teams that already standardized on LINE and want to keep using it - not as a gating dependency. The integration is included in every paid Inflowave plan with no per-event surcharge.
7-day free trial. Up to 50 Instagram accounts. Cancel any time.