Using the WebUI — connecting each service under 「API 連携」
Any service not listed here cannot be connected under 「API 連携」. Headings quote the screen's own wording.
Part of the connections guide (references/webui-connections.md: the 3 tabs, connectors, saving credentials from chat, asking an admin, your own MCP server, your company's own OAuth client, sharing an account). Other topics:
conversations, the input box, and sign-in: references/webui.md;
documents, files, tables, memory, channels, and apps: references/webui-workspace.md;
editing a file in place (「編集」): references/webui-file-edit.md;
SIROE pages, blocks, and boards: references/webui-siroe.md;
settings, administration, models, and triggers: references/webui-settings.md;
/office: references/webui-office.md;
/meetings: references/webui-meetings.md.
SAP Concur
Admins and managers connect by entering Concur's Client ID / Client Secret / Company ID / Company Request Token (the Company Request Token is issued on the Concur side and expires after 24 hours). 「チャットからできること」 in the same section lists, even before connecting, two groups: 「見る」 (your own expense report list, contents, and line items; expense policies and expense types; which Concur user you act as) and 「入力・提出する」 (enter a quick expense, create an empty expense report, submit a report for approval; by default a confirmation appears before execution). After connecting, each person presses 「自分の Concur アカウントを確認する」 once — this links them to the Concur user whose login ID matches their email address, and from chat they can act only as that user. Unconfirmed people cannot use Concur from chat (an unverified sign-in email fails the confirmation). The connection expires after about 6 months unused; a warning shows when under 14 days remain. Disconnecting goes through a confirmation dialog — it discards the company token, clears every member's identity confirmation (each confirms again after reconnecting), and asks Concur to revoke Samurai App's authorization. Reconnecting with a different Company ID without disconnecting also clears identity confirmations.
SmartHR
Admins and managers connect by entering the environment (本番 / サンドボックス), the subdomain (the start of the SmartHR URL), and an access token (issued in SmartHR under 「共通設定 → 外部システム連携 → アクセストークン」). The token never expires (no warning). If the token's 「アクセス制限ルール」 restricts IP addresses, the connection fails. Chat can read only up to the company's employee directory (search employees, view one person, list departments, employment types, and offices), and registering, updating, and inviting employees and creating departments are limited to admins and managers (by default a confirmation appears before execution). Salary, withholding tax, My Number, family, bank account, pension number, and residence card information cannot be read or written from chat. Each person presses 「自分の SmartHR アカウントを確認する」 once — this links them to the SmartHR user with the same email address; people not registered as employees in SmartHR cannot confirm and cannot use SmartHR from chat. SmartHR has no way to look a user up by email, so confirmation reads through the first 3,000 users only — in a company with more than 3,000 SmartHR users, people beyond that may not be able to confirm. Disconnecting, as with Concur, goes through a confirmation dialog and clears everyone's identity confirmation (the token itself is deleted in SmartHR's admin screen). Reconnecting with a different subdomain also clears identity confirmations.
HRMOS勤怠
Admins and managers connect by entering the company string (the per-company string at the end of the HRMOS勤怠 login URL) and the Secret Key of an API KEY issued in the HRMOS勤怠 admin screen. Tokens are reissued from the stored Secret Key (no expiry warning). What can be done from chat is listed in 「チャットからできること」 in 3 groups — 「自分の勤怠を見る」 (anyone: your own monthly attendance and totals of actual working hours, overtime, and late-night hours; punch history; remaining leave; lists of work categories, departments, employment types, locations, and leave types), 「打刻・修正する」 (your own records only: clock-in, clock-out, and break punches use the current time only; past times are handled by correcting the clock-in/out and break times for your own day; by default a confirmation appears before execution), and 「全社の勤怠を見る」 (admins and managers only: employee list, company-wide or other employees' monthly attendance, company-wide attendance for a given day, monthly reports, other employees' remaining leave). Punching or correcting for other employees, applying for or approving month-end closing, year-end adjustment documents, and punch location information cannot be handled from chat. Each person presses 「自分の HRMOS勤怠 アカウントを確認する」 once (matched by email); unconfirmed people cannot use it from chat. Disconnecting (confirmation dialog) or reconnecting with a different company string clears everyone's identity confirmation (delete the API KEY itself in the HRMOS勤怠 admin screen)
LegalOn
Unlike the other SaaS, admins and managers only choose the region to use and enable it (no company-level key is entered). To use it from chat, each person issues their own API credential in LegalOn under [個人設定] → [API連携] and registers their own on this screen. If the credential expires or is revoked, reissue it the same way and register again. The contracts a person can view and write are exactly those allowed by their permissions in LegalOn, and there is no way to act with someone else's permissions.
スマレジ
Admins and managers connect by entering the environment (本番 / サンドボックス), contract ID (契約 ID), Client ID, and Client Secret (the values from the app in スマレジ・デベロッパーズ). If pos.transactions:read and pos.staffs:read are not enabled in the app's 「スコープ」, the missing names are shown and the connection fails. Tokens are re-fetched on expiry (no warning). The only thing it can do is view provisional sales (仮販売) (list by period, store, and status; the line items of one record; period up to 31 days), and confirmed people can read all stores under the contract. Cost prices, member information, and staff names are not shown, and nothing can be registered or cancelled. Each person presses 「自分のスマレジアカウントを確認する」 once — this links them to the staff member with the same email address; people without such a staff record, and suspended staff, cannot confirm. Disconnecting, and reconnecting with a different contract ID or environment, also clears identity confirmations
ジョブカン経費精算
Admins and managers connect by entering an API token issued in the ジョブカン経費精算 admin screen. The token never expires (no warning). Chat can read your own requests (申請書) (status, line items, approval progress, and comments for expense reimbursement, payment requests, general, and EC purchase requests) and lists of forms, groups, positions, projects, and business partners; admins and managers can search everyone's requests by applicant, group, project, period, and status. The user list and registering/updating master data (projects, business partners, groups, positions) are limited to admins and managers (by default a confirmation appears before execution). Requests cannot be created, approved, or sent back from chat (the Jobcan API has no endpoint for it, so do it in the Jobcan screen). Bank account information and users' special notes cannot be read or written. Each person presses 「自分のジョブカンアカウントを確認する」 once — this links them to the Jobcan user with the same email address; users without a staff code cannot confirm. Disconnecting (confirmation dialog) and every reconnection clear everyone's identity confirmation — the token alone cannot identify the company.
クラウドサイン
The same two-step setup as LegalOn. Admins and managers enable it by entering the environment (本番 / サンドボックス) and their own client ID — the client ID entered here is not saved; it is used only to check that the connection works and which team it belongs to. To use it from chat, each person issues their own under [アカウント] → [クライアント ID] in クラウドサイン and registers it on this screen. Registration succeeds only when the email address of the クラウドサイン user tied to that client ID matches the email address you are signed in with (with an unverified email address, registration itself fails). A client ID for a different team is also refused. Accounts using the multi-department management feature (複数部署管理機能) cannot connect, and neither can accounts on the エンタープライズプラン — クラウドサイン's own help says the API that returns your own user (which registration uses to identify you) and the team's document list are unavailable on that plan; such accounts see 「複数部署管理機能を使っているアカウントは、この連携に対応していません」. From chat you can only view the list of your own documents and the team's documents, a document's contents (recipients, status, and files), and document information (counterparty, execution date, contract period, cancellation notice deadline, auto-renewal, control number, transaction amount), and update that document information. Sending, reminding, rejecting, or cancelling documents, and creating or downloading documents or files, cannot be done. Listing the team's documents requires document management permission on the クラウドサイン side. 「クライアント ID の登録を削除する」 removes your own. Disconnecting goes through a confirmation dialog and discards the client IDs deposited by all members (after reconnecting, each person registers again).
カオナビ
Admins and managers connect by entering the Consumer Key and Consumer Secret issued in カオナビ under 「管理者機能トップ → 公開API v2 情報 → 認証情報」. What chat can reach is limited to the resources and sheets selected under that credential's 「操作対象」 (all off by default; sheets can be selected one by one, so turn off in カオナビ any sheet you do not want read). Identity confirmation needs access to 「ユーザー情報」, so leaving it off causes the connection to be refused. Chat can read the company's member directory and the enabled sheets (search members, view one person, the department tree, the list and contents of sheets, basic information fields, and the progress of registrations/updates), and registering and updating members and updating sheets or adding records are limited to admins and managers (by default a confirmation appears before execution). Gender, date of birth, and age cannot be read from chat. カオナビ processes registrations and updates later: at first they are only accepted, and complete once the progress says so. Each person presses 「自分のカオナビアカウントを確認する」 once — this links them to the カオナビ user with the same email address, and only people registered as users who can log in to カオナビ and who are tied to a member can use it. Disconnecting (confirmation dialog) or a different Consumer Key clears everyone's identity confirmation (delete the credential itself in カオナビ's admin functions)
Sansan
As with LegalOn, admins and managers enable it, then each person registers their own API key (Sansan's top-right menu → [設定] → [API キー]; needs API permission from the Sansan admin). Chat can only read business cards, persons, tags, and contacts, within their Sansan permissions. A revoked key drops the registration. Disconnecting discards everyone's keys.
SmartDB
Admins and managers connect by entering the subdomain (the part right after https:// up to the first 「.」 in SmartDB's URL) and a binder token issued in SmartDB under 「システム管理 → バインダトークン」. For each binder you want chat to reach, register this token in that binder's 「トークン設定」 — only those binders are reachable. If the token's 「IP アドレス制限」 is set, the connection fails (the sending IP address is not fixed). The token never expires (no warning). Calls run as the token's robot user, not as the person in the conversation, so there is no identity confirmation and everyone in the tenant can read the documents of the reachable binders. Chat can list binders, read a binder's form, list views, search a view's documents (by item values or free text, up to 100 per call, 25 by default), and read one document; registering and updating documents are limited to admins and managers (by default a confirmation appears before execution), and SmartDB records the robot user as the registrant. Deleting documents, CSV, attachments, comments, processes, and full-text search are not available. Disconnecting goes through a confirmation dialog and discards the token (delete the token itself in SmartDB's admin screen).
LINE WORKS
Separate from the 「外部チャット」 bot. Admins and managers enter the Developer Console app's Client ID, Client Secret, Service Account, and Private Key; its OAuth Scopes need user.read, orgunit.read, group.read, calendar, and board. Chat reads the address book and boards company-wide and your own calendar; adding, changing, or deleting your own events needs a confirmation, and posting to boards is admins and managers only. Tasks, others' calendars, and phone numbers or birthdays are out of reach. Each person presses 「自分の LINE WORKS アカウントを確認する」 once (matched by login email). Disconnecting or a new Client ID clears everyone's confirmation
note
Not an official API: it uses note's internal web API, so it may stop when note changes, and enabling asks admins and managers to confirm that. Once enabled, chat reads public articles, creators, magazines, hashtags, comments, and contests with no registration. For your own articles, page views, and drafts, each person registers their _note_session_v5 cookie value (copy it from the developer tools while logged in to note.com). It opens your whole note account; Samurai App uses it only for the listed actions. Chat reads and creates drafts; you publish on note. Logging out drops it; disconnecting discards everyone's.