kintone

kintone

This connector uses the kintone REST API (https://<your domain>/k/v1) of kintone by Cybozu, the no-code business app platform used across Japan: apps and their form fields, layout, views and process management, records with kintone queries and cursors, record creation and updates, comments, process status changes, file upload and download, and spaces with their members and threads. Guest spaces (/k/guest/...) are not covered.

Setup (about 5 minutes)

1. Enter your kintone domain in KINTONE_DOMAIN, the host of your kintone URL without https:// and path: example.cybozu.com (Japan), example.kintone.com (US and other regions) or example.cybozu.cn. Domains behind Basic authentication or client certificates (セキュアアクセス) are not supported.
2. Choose how the connector signs in. You can set one or both:
   • API token (KINTONE_API_TOKEN, recommended for a few apps): open the app, アプリの設定 (App Settings), tab 設定 (App Settings), APIトークン (API Token), 生成する (Generate). Tick only the permissions the AI needs: レコード閲覧 (View records), レコード追加 (Add records), レコード編集 (Edit records), and レコード削除 (Delete records) only if you switch on kintone_delete_records. Save, then click アプリを更新 (Update App), or the token stays inactive. One token covers one app; for several apps join their tokens with commas (up to 9). Writes made with a token show the user Administrator.
   • Password login (KINTONE_PASSWORD_AUTH): the Base64 text of login name:password of a kintone user, e.g. made with printf '%s' 'login:password' | base64. The connector then acts as that user and sees every app, space and record the user may see; it is also the only way to list apps and read spaces. Use a dedicated integration user with the rights you want the AI to have. When both are set, kintone uses the password login.
3. Install. The install check (kintone_get_api_list) only proves the domain answers; run kintone_get_app with an app id to check the token, or kintone_list_apps to check the password login.

Workflow

• Find apps: kintone_list_apps (password login) or ask the user for the app id (the number after /k/ in the app URL); kintone_get_app and kintone_get_app_settings describe one app. kintone_get_api_list lists what the domain offers.
• Learn the app before touching records: kintone_get_form_fields gives every field code, type and option list; kintone_get_form_layout the visual grouping; kintone_list_views the saved views (a view filterCond can be reused as a query); kintone_get_process_management the statuses and actions.
• Read records: kintone_get_record for one id, kintone_list_records with a query for up to 500 at a time (add limit and offset inside the query). Beyond 10,000 records use kintone_create_cursor, then kintone_get_cursor_records until next is false, and kintone_delete_cursor to stop early.
• Write records: kintone_create_record or kintone_create_records (up to 100), kintone_update_record by id or a unique field, kintone_update_records for up to 100 changes or an upsert. Read the record first and send revision when several people edit the same app.
• Process management: kintone_update_status runs an action (e.g. 承認する) and kintone_update_assignees changes the 作業者.
• Comments: kintone_list_comments reads, kintone_add_comment posts with optional mentions.
• Files: kintone_download_file with the fileKey from a FILE field; kintone_upload_file returns a temporary fileKey, which you then write into a FILE field.
• Spaces (password login only): kintone_get_space, kintone_list_space_members, kintone_add_thread_comment.

Queries (query): field codes, not labels, with operators =, !=, >, <, >=, <=, in ("a", "b"), not in, like "text" (text fields), joined by and / or, then order by field asc|desc, limit n (at most 500) and offset n (at most 10,000). Dates are "2026-10-30", date-times UTC "2026-10-30T00:00:00Z"; functions TODAY(), THIS_MONTH(), LAST_WEEK(), LOGINUSER(). Drop-down, radio and status values must match the option text exactly (e.g. ステータス in ("完了")).

Reading answers: every field is {"type": ..., "value": ...}. Numbers and calculated values come as strings; date-times are UTC; $id is the record id and $revision its version. USER_SELECT and CREATOR values are {code, name} with the login name in code. FILE values list fileKey, name, contentType and size.

Limits: 10,000 requests per app per day and 100 parallel requests per domain; 500 records per read, 100 per bulk write or delete, 10 comments per page, 10 open cursors per domain (each lives 10 minutes). Uploaded files must be attached within 3 days.

Errors: kintone answers with code, message and, for input errors, errors per field. CB_VA01 is invalid input (wrong field code, bad date, missing required field: read errors). CB_NO02 means the token or user lacks the permission, or the token belongs to another app. CB_WA01 is a failed password login. A 404 HTML page usually means a wrong KINTONE_DOMAIN.

Switched off at install: kintone_delete_records; it cannot be undone, so an admin switches it on when the team needs it.