Communication · Integration
LINE WORKS
Add LINE WORKS to your product for your customers, and give your AI agents governed access to it.
Embed a LINE WORKS integration so your customers get updates from your product in the workspace their teams already use, sent from their own tenant under their own permissions. You never proxy through a shared account, so a customer revoking access affects only their own connection, and sends are deduplicated per event so a retry does not post the same message twice. fastn handles per-customer OAuth, token refresh and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own LINE WORKS workspace so your product posts where their teams already look.
Send a message to a member or a group when a workflow in your product needs attention.
Read the members and groups in a workspace so a customer picks the right destination during onboarding.
Create a calendar event from something scheduled in your product, in the customer's own calendar.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent posts an update to the group the customer nominated, within governed permissions.
An agent looks up who is in a group before deciding how to phrase a message.
Every send runs under the customer's own workspace grant and is logged per tenant.
Example prompt
Send this shift change to the store group and add a calendar entry for the handover.
Set up LINE WORKS in 4 steps
- 01Open the LINE WORKS connector from your fastn dashboard.
- 02Have each customer authorise their own LINE WORKS workspace with OAuth.
- 03Map the members, groups and calendars your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the LINE WORKS integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a LINE WORKS integration without building it. Your customers connect their own LINE WORKS account inside your product and work their messages, conversations and participants there, with no per-customer code on your side.
- Handle the part that actually costs time: anything sent is user-visible, so duplicates and misfires are immediately embarrassing. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a LINE WORKS update is not your on-call problem.
- One integration serves your product and your agents. The same governed LINE WORKS connection powers in-product features and gives AI agents scoped, audited access, so you put the right message in front of the right team automatically without wiring it twice.
Used by these teams
Compare with
Slack
Microsoft Teams
LINEOften used alongside
Tools the same teams tend to run next to LINE WORKS, across other categories.
Aircall
Calendly
Gong
Google CalendarLINE WORKS integration FAQ
How do I add a LINE WORKS integration to my product?
Enable the LINE WORKS connector in your fastn dashboard, then let each customer authenticate their own LINE WORKS account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no LINE WORKS client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own LINE WORKS account?
Yes. Every connection is scoped to the individual customer, so each authorises their own LINE WORKS account and only ever sees their own messages, conversations and participants. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this LINE WORKS integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent posts an update to the group the customer nominated, within governed permissions.
Who maintains the LINE WORKS integration?
fastn does. When LINE WORKS changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does each customer connect their own LINE WORKS account?
Yes. Every customer authorises their own LINE WORKS account, so messages, meetings and notifications originate from their workspace under their permissions. You never proxy through a shared account, which also means a customer revoking access affects only their own connection.
How are duplicate notifications avoided?
Sends are deduplicated per event, so a retry after a network failure does not post the same message twice into a channel people are reading.
What can I build with the LINE WORKS integration?
A common starting point: connect their own LINE WORKS workspace so your product posts where their teams already look. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the LINE WORKS integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding LINE WORKS does not change your per-connector cost. You can start free with 3 connected accounts.
Add LINE WORKS to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.