Integrations · LINE
In Japan, Taiwan and Thailand, LINE is the customer relationship.
We connect LINE Official Accounts to monday.com, HubSpot and your ERP, so a friend-add becomes a contact record with consent attached — and the conversation stops ending at the Official Account Manager.
LINE gives you a display name, an icon, a status message and a language. It will not give you a phone number, an email address or a way to re-read a message you failed to store. Everything a CRM needs, you have to capture yourself.
That is the whole engineering problem, and it is why LINE projects that start as "just connect the chat tool" end up rebuilt. We design the persistence and consent layer first, because LINE keeps no logs for you and will not hand the data back.
Clients who have used our messaging integration services
Where it matters
Three markets where LINE is not one channel among several.
Figures are LY Corporation’s own, as at 31 March 2026. LINE counts accounts that launched the app at least once in the month, so read these as account-launch metrics rather than deduplicated people.
Japan
100m monthly actives
81.3% of the population. LINE is the default messaging layer for consumers and, increasingly, for service delivery.
Taiwan
22m monthly actives
94.5% of the population — the highest penetration of any LINE market.
Thailand
54m monthly actives
81.8% of the population. LINE Thailand reported 12 billion Official Account conversations across 2025.
Elsewhere
193m globally
LY Corporation frames LINE’s overseas business as Taiwan and Thailand. It no longer reports Indonesia as a core market.
The pipe
From a friend-add to a contact record with consent
A friend-add gives you an opaque user ID and nothing else. The integration is everything that turns that ID into a customer you can actually contact.
- LINE OAfollow webhook · userId
- LIFF formPhone, email, explicit consent
- monday.com / HubSpotContact keyed on userId
- Push & rich menuFollow-up · booking · order status
The reply to a follow event is free and does not consume your message quota — which makes a conversational design structurally cheaper than a broadcast one.
Your stack
Three of these support LINE natively. Two do not.
If a vendor tells you LINE needs custom work everywhere, they have not checked. The gap is real, but it is specific — and it is exactly where most of our clients sit.
PlatformSupportOut of the boxWhat we build
Salesforce
Native
Out of the boxLINE is a first-class Messaging channel in Service Cloud, and Salesforce appears directly in LINE’s own technology-partner directory.
What we buildWork around the documented gaps: agents can receive but not send audio, documents do not pass in either direction, and LINE’s unsend is not honoured in transcripts.
Microsoft Dynamics 365
Native
Out of the boxA standard out-of-the-box social channel, built by Microsoft rather than co-built with LINE.
What we buildIdentity resolution against existing contacts, and everything past the channel itself — consent state, routing, and the rest of the estate.
Zoho SalesIQ
Native
Out of the boxLINE sits alongside WhatsApp, Telegram and WeChat in SalesIQ.
What we buildCross-suite flows the moment LINE has to reach anything outside Zoho, and the LIFF capture step SalesIQ does not provide.
HubSpot
Not native
Out of the boxNo LINE channel. HubSpot’s own documentation routes you to the Custom Channels API, which needs Sales Hub or Service Hub Professional plus HubSpot Credits.
What we buildThe custom channel itself — webhook, signature validation, identity mapping and inbox threading — so LINE behaves like a first-party channel to your team.
monday.com
Not native
Out of the boxNothing. No app, no channel, no listing. monday.com does not appear in LINE’s partner directory, and LINE does not appear in monday’s marketplace.
What we buildThe whole path: Messaging API webhook into monday’s GraphQL, plus the persistence layer LINE forces on you because it will not re-serve an inbound message.
Verified against each vendor’s documentation and LINE’s technology-partner directory in September 2026. Third-party middleware exists in this space — SleekFlow, Omnichat, Crescendo Lab and others — and we will tell you when buying one beats building.
What we build
The layer LINEdeliberately leaves to you.
Documented, owned by a named maintainer, and handed over with the architecture written down.
🏗️
Provider & channel architecture
The decision that cannot be undone: which provider owns which channels, so your user IDs stay consistent as you add LINE Login, LIFF and a second Official Account.
📝
LIFF lead capture
The form that turns an anonymous user ID into a contactable person, with explicit consent captured in the same step.
🗄️
Message persistence
Durable storage of inbound events and media, because LINE serves each one exactly once and keeps no logs on your behalf.
🔗
Account linking
LINE’s security-hardened flow for binding a LINE identity to an existing customer record, rather than the home-grown version LINE warns against.
🍱
Rich menus & segmentation
Per-user rich menus driven from CRM state, plus the audience work the API cannot reach and that has to be designed around.
💴
Quota design
Costing the plan against your real send pattern. Replies and 1:1 chat are quota-exempt in Japan, so conversational designs cost less than broadcast ones.
Platform rules
LINE’s constraints are stricter than most teams assume.
Several of these cannot be retrofitted. Getting them wrong at the start means rebuilding, not patching.
- Channels per account
- Normally one Messaging API channel per Official Account
- What it meansA client already running a vendor chat tool on their OA cannot simply add a second integration. The module-channel escape hatch is gated behind a corporate application.
- User IDs
- Provider-scoped, not channel-scoped
- What it meansUnder one provider, LINE Login and the Messaging API return the same ID, so no linking step is needed. Across providers they differ, and the choice cannot be changed later. Consolidate on day one.
- Inbound messages
- Delivered once, by webhook, and never re-servable
- What it meansThere is no API to fetch an inbound message again. Miss the webhook and the content is gone permanently, which makes durable persistence a requirement rather than a nicety.
- Logs
- LINE keeps none on your behalf
- What it meansIn LINE’s words, you are responsible for saving logs. Any audit or dispute you expect to win later depends on storage you built yourself.
- Reply tokens
- Single-use, valid one minute
- What it meansFree and quota-exempt, which makes them worth engineering for. But a slow downstream call costs you the free reply and pushes you onto a billed push message.
- Contact data
- Display name, icon, status and language. Nothing else
- What it meansPhone and email come from a LIFF form, a conversation, or a separate LINE application for the email scope. PC-only users cannot consent to profile access at all, so your schema has to tolerate a nameless contact.
- Data retention
- Friend and group information must not be stored beyond 24 hours
- What it meansLINE’s User Data Policy also treats your CRM vendor, iPaaS and any LLM API as contractors, with obligations that must be flowed down to them.
- Opt-out
- Blocking you is the only signal
- What it meansA friend-add is a channel, not consent. A disengaged user generates no event at all, so engagement state has to be inferred rather than read.
Verified against LINE’s Messaging API documentation, development guidelines and User Data Policy in September 2026. LINE declines to publish a retention period for media content, so we do not quote one.
What this looks like in your industry
The Official Account as the storefront, not the leaflet
Friend-add from a QR code in store, a rich menu that exposes ordering and order status, and every interaction keyed to a CRM record. Central Chat & Shop in Thailand runs this pattern at over a thousand customer conversations a day.
Benefits
In-store QR capture straight into the CRM with consent
Rich menu wired to ordering, pickup and order status
Loyalty state read from the CRM and reflected per user
Narrowcast segments built from CRM data, not guesswork
Why LINE projects get rebuilt
Four decisions that are cheap at the start and expensive to reverse.
01
The provider was chosen by whoever set it up Channels cannot move between providers, and user IDs differ per provider. Get this wrong and consolidating later means re-identifying every contact.
02
The Official Account is already occupied A vendor chat tool holds the one Messaging API channel. The integration you scoped cannot be installed alongside it.
03
Nobody stored the inbound messages LINE serves each webhook once and keeps no logs. The conversation history you assumed you could export was never retained.
04
The automation platform turned out not to support it n8n’s LINE node is deprecated and non-functional since LINE Notify closed. Zapier has no LINE app at all. Plans built on either have to start again.
How the engagementactually runs
Fixed phases, defined outcomes, published fees. You always know what is being delivered, by when, and at what cost.
01
Account & provider audit
What Official Accounts exist, which provider owns them, what already occupies the Messaging API channel, and whether your verification status supports what you want to send.
02
Identity & consent design
How a user ID becomes a contact, where the LIFF capture sits, what consent wording you use, and how that satisfies PDPA or APPI as well as LINE’s own data policy.
03
Build, with persistence first
Signature validation, durable event storage, retries and alerting — before any of the features, because LINE will not give you a second chance at an inbound message.
04
Handover you can maintain
Architecture documentation, a named maintenance path, and your team trained on the parts they will change. No mystery middleware.
Book a time
Talk to a consultant who has shipped this
Thirty minutes. We will tell you what your Official Account can and cannot support before we quote you anything.
contact@fruitionservices.ioSydney · New York · London · Singapore · New Delhi · Manila
Platinum monday.com partner · 900+ implementations
Frequently asked questions
Not with anything you can buy. monday.com has no LINE app in its marketplace and does not appear in LINE’s technology-partner directory, so there is no product to install. We build the path directly: a LINE Messaging API webhook with signature validation, a durable store for inbound events, identity resolution, and writes into monday’s GraphQL API so a conversation becomes an item with updates and a status your existing automations already react to.
Make LINE part of the system,
Book a 30-minute discovery call. We will give you a frank read on scope, fit and cost.