LINE
for LuumenAI
Read your LINE account's menus and delivery counts, then change them with approval
Connect a LINE Official Account's Messaging API channel and Luumen can read it directly from the terminal: rich-menu definitions, which menus exist, follower and group member IDs, and how many messages went out on a given UTC+9 date. Changes — creating a menu, swapping the default, sending a push message — are previewed and sent for approval first. Luumen authenticates with an API key.
The LINE toolbox
15 tools: 6 read, 9 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadDownload Message Content PreviewDownload LINE's reduced-size preview image for a retained image or video message whose contentProvider.type is line.
- ReadGet Message Delivery CountGet the number of reply, push, multicast, or broadcast messages sent on one UTC+9 calendar date.
- ReadGet Rich MenuGet one Messaging API rich-menu definition by ID, including its canvas, tappable areas, and actions.
- ReadList Chat Member IDsReturn one page of member user IDs for a group or legacy room containing the bot.
- ReadList Follower IDsReturn one page of user IDs for friends of the LINE Official Account.
- ReadList Rich MenusList all rich menus created through the Messaging API.
- WriteCreate Rich MenuCreate a rich-menu definition and return its ID. Approval by default
- WriteCreate Rich Menu with ImageCreate a rich-menu definition and upload its JPEG or PNG image in one call. Approval by default
- WriteDelete Rich MenuPermanently delete a rich menu by ID. Approval by default
- WriteLink or Unlink User Rich MenuLink or unlink a per-user rich menu. Approval by default
- WriteMark Messages as ReadMark all messages through a webhook-issued read token as read. Approval by default
- WriteReply to MessageReply with one to five text messages using a single-use token from a LINE webhook. Approval by default
- WriteSend Push MessageIrreversibly send one to five text messages from a LINE Official Account to a webhook/API userId, groupId, or roomId. Approval by default
- WriteSet or Clear Default Rich MenuSet or clear the Messaging API default rich menu. Approval by default
- WriteUpload Rich Menu ImageUpload a JPEG or PNG image for a rich menu. Approval by default
One prompt, start to finish
What a governed LINE run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create rich menu, create rich menu with image, delete rich menu, link or unlink user rich menu, and more — is shown as a plan and requires approval by default, including the 6 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to LINE — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
SlackRead the incident thread; post updates and approvals back.
GmailVendor and alert mail as context; replies drafted for review.
Microsoft TeamsRead Teams channels and chats for context, then make membership changes as approved steps.
DiscordRead Discord command permissions and app context, then change them with approvalPut LINE to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.