line-client

What This Skill Does

The line-client skill for OpenClaw enables full-featured LINE messaging integration by interfacing with the LINE Chrome extension gateway. It acts as an automated bridge, allowing the AI agent to send and receive messages, manage your contacts and groups, update profile information, and handle reactions. By leveraging the line-chrome-gw.line-apps.com gateway, it provides an HMAC-signed API that mirrors the functionality of the official LINE desktop client, wrapped in a developer-friendly Python interface.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/2manslkh/line-client

Ensure that you have the required Node.js environment configured to support the signer.js utility, as it is critical for the HMAC signing process that authenticates your requests to the LINE servers. You will also need to ensure that lstm.wasm and lstmSandbox.js are present in your root workspace to support the authentication flow.

Use Cases

This skill is perfect for users who want to automate their personal or professional LINE workflows. Common use cases include:

• Automated Alerts: Send automated notifications to your LINE groups based on system monitoring or webhook triggers.
• Customer Support: Manage inbound LINE queries automatically or draft responses for human approval.
• Smart Assistant Integration: Connect your existing AI agents to your LINE account to handle messages while you are away.
• Contact Management: Sync and organize your friends list programmatically.

Example Prompts

1. "Check my latest messages from the 'Work' group and summarize any urgent tasks."
2. "Send a message to my friend Ken saying: 'I'll be running 10 minutes late for dinner.'"
3. "Update my LINE profile status to 'Working on AI projects' and fetch my current contact list."

Tips & Limitations

Authentication is handled via a QR-code login flow. Please note that the authorization tokens provided by this method expire approximately every 7 days; when you encounter an APIError(10051), you must trigger the re-authentication sequence.

Crucial Security Note: When the on_pin event triggers during QR login, you have approximately 60 seconds to provide the user with the 6-digit PIN. Delays will cause the session to time out. Always ensure the signer.js process is running on port 18944 before attempting to initialize the LineChromeClient to prevent connection errors.