Skip to main content

LINE WORKS

Shanone’s LINE WORKS integration gives your agent 350 tools — the largest in Shanone’s catalog — covering everyday messaging, mail, calendar, and drive alongside deep directory administration (users, groups, org units, custom fields) and bot management.

Getting Started

1

Register a LINE WORKS Developer app

In the LINE WORKS Developer Console, create an app and generate a Client ID, Client Secret, and a Service Account with a private key for JWT-based authentication.
2

Add all four credentials in Shanone

Go to Integrations > LINE WORKS in the Shanone dashboard and enter the Client ID, Client Secret, Service Account, and Private Key — all four are required to mint access tokens.
3

Retry your request

Once saved, shanone_execute_tool calls for lineworks_* tools will succeed.

Available Tools

Shanone provides 350 tools for LINE WORKS, organized into these categories:
File/folder CRUD, sharing, permissions, revisions, links, and trash across your own drive, shared drives, group folders, and channel folders — e.g. lineworks_upload_drive_file, lineworks_create_drive_permission, lineworks_list_drive_file_revisions, lineworks_create_drive_file_link
Member lifecycle, profile, status, and account linking — e.g. lineworks_create_member, lineworks_search_members, lineworks_suspend_member, lineworks_grant_member_link_to_works, lineworks_resolve_member_by_external_key
Boards, posts, comments, and attachments — e.g. lineworks_create_board, lineworks_create_board_post, lineworks_search_board_posts, lineworks_create_board_post_comment
Company/personal contacts, tags, custom properties, and photos — e.g. lineworks_create_contact, lineworks_search_user_contacts, lineworks_create_contact_custom_properties
Org hierarchy levels and job positions — e.g. lineworks_create_level, lineworks_create_position, lineworks_enable_levels
Personal and default calendars plus events — e.g. lineworks_create_calendar_event, lineworks_search_calendar_events, lineworks_update_default_calendar_event
Tasks and task categories — e.g. lineworks_create_task, lineworks_complete_task, lineworks_create_task_category
Sending, folders, filters, and forwarding — e.g. lineworks_send_mail, lineworks_create_mail_filter, lineworks_enable_mail_forwarding
Groups, members, administrators, and external keys — e.g. lineworks_create_group, lineworks_add_group_administrator, lineworks_update_group_external_keys
Creating/updating bots and bot domains — e.g. lineworks_create_bot, lineworks_register_bot_domain, lineworks_add_bot_domain_member
Group notes and note posts — e.g. lineworks_create_group_note, lineworks_create_group_note_post, lineworks_search_group_note_posts
Org unit access restrictions by member, user type, and team — e.g. lineworks_set_member_orgunit_access_restrict, lineworks_set_team_orgunit_access_restrict
Teams and team membership — e.g. lineworks_create_team, lineworks_get_team_members, lineworks_move_team
Custom fields and member custom properties — e.g. lineworks_create_custom_field, lineworks_create_member_custom_properties
Custom user types and profile statuses — e.g. lineworks_create_user_type, lineworks_create_profile_status
External key mapping for levels, positions, and user types — e.g. lineworks_update_level_external_keys, lineworks_list_position_external_keys
Direct/channel messaging and read-only bot/user/channel lookups — e.g. lineworks_send_message_to_user, lineworks_send_message_to_channel, lineworks_create_channel, lineworks_list_users
Bot attachments, audit/monitoring log downloads, and external browser policy — e.g. lineworks_upload_bot_attachment, lineworks_download_audit_logs, lineworks_enable_external_browser

Common Use Cases

Employee onboarding

Create a member, assign org unit/level/position, and send an invitation email

Intranet content ops

Post company announcements to a board and track must-read acknowledgment

Compliance exports

Download audit and monitoring logs for a security review

Document collaboration

Share a Drive folder with fine-grained permissions and track file revisions

Troubleshooting

LINE WORKS uses JWT-based service account auth, not a simple bearer token — Client ID, Client Secret, Service Account, and Private Key must all be correctly set; a single missing or malformed field prevents any token from being issued.
These tools require the connected app to have Directory Management API scopes granted in the Developer Console for that app — messaging-only scopes aren’t sufficient.
Standard delete is often a soft-delete/deactivation; use lineworks_force_delete_member if you need to permanently and immediately remove a member record.