How to connect LINE to OpenClaw
Connect LINE to OpenClaw with ClawLink: paste your LINE key once and 13 tools work from chat. No MCP server to run, nothing stored on your machine.
LINEAPI KEYMCPUse a LINE Official Account's Messaging API channel to manage messages, audiences, and rich menus.. Once connected, OpenClaw can read and act on LINE from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to LINE access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical LINE setup: install one ClawHub skill, connect LINE in the browser, and OpenClaw can call real LINE actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to LINE.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect LINE
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with LINE?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect LINE in the ClawLink dashboard — paste your LINE API key once.
Verify the connection by asking OpenClaw:
Use LINE to download message content preview and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once LINE is connected in the dashboard, that agent calls the same 13 LINE tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
LINE MCP for OpenClaw
Looking for a LINE MCP server for OpenClaw? ClawLink connects LINE to OpenClaw and exposes 13 LINE tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes LINE integration works the same way.
What the OpenClaw LINE integration can do
13 LINE tools are ready for OpenClaw once the account is connected. The 12 below are the ones people reach for most; your agent can call all 13.
12 of 13 LINE tools for OpenClaw
| Tool | What it does |
|---|---|
Download message content preview line_download_message_content_preview | Download LINE's reduced-size preview image for a retained image or video message whose |
Get message delivery count line_get_message_delivery_count | Get the number of reply, push, multicast, or broadcast messages sent on one UTC+9 calendar date |
Get rich menu line_get_rich_menu | Get one Messaging API rich-menu definition by ID, including its canvas, tappable areas, and |
List chat member IDS line_list_chat_member_ids | Return one page of member user IDs for a group or legacy room containing the bot |
List follower IDS line_list_follower_ids | Return one page of user IDs for friends of the LINE Official Account |
List rich menus line_list_rich_menus | List all rich menus created through the Messaging API |
Create rich menu line_create_rich_menu | Create a rich-menu definition and return its ID |
Link or unlink user rich menu line_link_or_unlink_user_rich_menu | Link or unlink a per-user rich menu |
Set or clear default rich menu line_set_or_clear_default_rich_menu | Set or clear the Messaging API default rich menu |
Create rich menu with image line_create_rich_menu_with_image | Create a rich-menu definition and upload its JPEG or PNG image in one call |
Mark messages as read line_mark_messages_as_read | Mark all messages through a webhook-issued read token as read |
Upload rich menu image line_upload_rich_menu_image | Upload a JPEG or PNG image for a rich menu |
Try it: find the LINE tool you need
Browse the 12 LINE tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use LINE to download message content preview and walk me through the result in plain English.
Pull the relevant data from LINE, summarize it in plain English, and point out anything that needs attention.
List the relevant items in LINE, group them by priority, and recommend what OpenClaw should do next.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want LINE working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the LINE API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected LINE account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for LINE. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right LINE actions to the runtime in a format your agent can reliably use. | 13 tools for LINE are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes LINE to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect LINE in the browser, and the 13 tools above work from chat. There is no SDK and no config file, and the LINE key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the LINE skill but can't call the tools
The ClawHub skill teaches OpenClaw about LINE, but the calls run through the ClawLink plugin and your connected account. Make sure LINE is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect LINE from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling LINE tools
LINE tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every LINE call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
LINE returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for LINE has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw LINE integration?
Yes. ClawLink is the fastest way to connect OpenClaw to LINE: link your LINE account once in the browser and OpenClaw can call the LINE API through 13 ready-made tools — no custom code or token handling.
How do I add LINE to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink LINE skill from ClawHub, then you click Connect in the dashboard to authorize LINE. OpenClaw calls the tools from the next message — no config files, and the LINE key you paste is stored server-side instead of in your environment.
How long does it take to connect LINE to OpenClaw?
About two minutes. Sign in, click Connect next to LINE in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring LINE up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want LINE working from chat.
OpenClaw installed the LINE skill but can't call the tools
The ClawHub skill teaches OpenClaw about LINE, but the calls run through the ClawLink plugin and your connected account. Make sure LINE is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
