Before a 1-on-1 or a performance review, it takes time to open the person's sheet in Kaonavi and reread past interview records and training history. After the meeting, you still have to add what you discussed to the sheet. This article is for HR staff and managers who use Kaonavi. It explains how to read members and sheets from AI chat through Kaonavi's public API, and how to add records to a sheet one at a time.
In Kaonavi, you can decide sheet by sheet which ones outside systems may read. This setting determines what the AI can read, so we cover it in detail in the steps.
The short answer
- Kaonavi has a public API (kaonavi API v2). An administrator checks the Consumer Key and Consumer Secret under "Admin Functions Top > Public API v2 Information > Credentials" and uses them
- What outside systems can read and write is chosen per credential in its "operation scope," resource by resource and sheet by sheet. Everything starts off
- Samurai App's Kaonavi integration uses this public API. From chat you can search members and read their basic information and the contents of sheets turned on in the operation scope
- Only Samurai App admins and managers can register and update members, and update sheets or add records. Kaonavi processes these later, so a request is first accepted and then applied after a short wait
Ways to connect Kaonavi data with other systems
Kaonavi's official site introduces the following ways to connect with outside systems.
| Method | What it is |
|---|---|
| API integration | Use the public kaonavi API v2 to fetch and update data from other systems |
| Custom CSV integration | Automate data updates via CSV, even with systems that have no automatic integration |
| RPA development | Get introduced to an RPA development partner who builds to your own specs and processes |
| taias I/F | Connect with a connector (iPaaS) provided by the partner ZERONI |
With API integration, you issue an access token from the Consumer Key and Consumer Secret and make calls with it. An access token is valid for 1 hour. The rate limit is 3,000 calls per hour per company, and updates are limited to 5 per minute per company. You can create up to 5 credentials, and the recommended practice is to split them by purpose and allow each only the operations it needs.
Kaonavi updates also have time-of-day rules. From 1:00 to 1:30 a.m., data backups run, and daily processing runs after that into the early morning; from around 2:00 a.m. to 5:00 a.m., the wait before an update starts can be long.
Using it from AI chat goes through the same public API. The rest of this article explains how.
What Samurai App can and cannot do
The operations listed under "What you can do from chat" in the settings screen fall into two groups. What they can reach is decided by the "operation scope" of the credential on the Kaonavi side.
View (anyone who has verified their account)
- Check which member you operate as
- Search members. Search by name, name reading, employee number, or department name, and filter by department. Former employees are included only when you ask. Up to 100 people per request, and the rest are read in turn
- Open one member and view their basic information and custom fields. Basic information is employee number, name and name reading, email address, hire and leave dates, years of service, department, and concurrent departments
- View the department tree
- Look up basic information fields (name, type, required, options)
- Look up the list of readable sheets and their fields
- View the contents of sheets for the members you specify. You can specify up to 20 people at a time
- Check the progress of registrations and updates
Register and update (admins and managers only; by default, a confirmation appears before it runs)
- Register a member
- Update a member's basic information (transfers, departures, field corrections, and so on). Only the fields you change are sent, and the rest stay as they are
- Update a sheet that holds one record per person
- Add one record to a sheet that holds multiple records. Existing records stay as they are
Every write covers one person at a time.
What it cannot do
- Read gender, date of birth, or age
- Delete members or sheet records
- Rewrite existing records in a multiple-record sheet. Rewriting replaces all of that member's records, so Samurai App refuses. Make corrections in Kaonavi's screens
- Read or write profile photos and attachments
- Manage Kaonavi users (the accounts that sign in) or permissions
- Read sheets turned off in the operation scope
Use 1: Reread a person's sheets before a 1-on-1
Before a meeting, read the person's basic information and past records together.
Find Yamamoto in Kaonavi and tell me their department and years of service.
Then list the records in the Interview Records sheet from newest to oldest, and sum up the issues we discussed up to last time in 3 points
The AI searches for the member, finds Interview Records in the list of readable sheets, and reads only that person's records. When you want to compare several people in the same department, you can specify up to 20 at once.
Look at the Training History sheet for the members of Sales Section 2, and make a table of the training each person has not taken yet
It can read only the sheets set in the operation scope on the Kaonavi side. For a sheet that does not appear in the list, ask your Kaonavi administrator to add it to the operation scope.
Use 2: Add one record to a sheet after the meeting
After the meeting, an admin or manager asks to add what was discussed to the sheet.
Add one record with today's date to the Interview Records sheet for employee number A0012.
Content: "Changed the second-half goal to 3 new client companies. Check progress next month"
The AI first reads the sheet's fields and shows an approval card that fits the date and content fields. When you allow it, Kaonavi has only accepted the request, and the processing happens later.
Is the record I just added done?
Ask this and it checks the progress. "OK" means it has been applied, and "NG" means there was an input error, with the reason returned. At night, it can take a while to apply because of Kaonavi's processing queue.
What you need
- A Kaonavi administrator (the person who checks the credentials and chooses the operation scope)
- A Samurai App admin or manager (the person who connects Kaonavi)
- A Samurai App account for each person who will use it. Their email address must match a user who can sign in to Kaonavi, and that user must be linked to a member
- A list of sheets to expose. Decide in advance which sheets chat may read
Steps
1. Choose the credential's "operation scope" in Kaonavi
A Kaonavi administrator opens "Admin Functions Top > Public API v2 Information > Credentials" and opens "Edit" for the credential to use. All operations start off.
- Always turn on fetching "User information." It is used for identity verification, and the connection is refused if it stays off
- Turning on fetching member information lets it search members and read basic information
- Sheets can be chosen one at a time. Leave off any sheet you do not want chat to read
- If you will also register or update from chat, check those operations too
Creating a credential just for Samurai App, separate from other integrations, makes it easier to change the scope later.
2. The administrator connects Kaonavi in Samurai App
Open the Connectors screen (/settings/connections) and press "Add API integration" on the "API integrations" tab. Choose Kaonavi from the list, and the settings fields open.
Enter the values of the credential from step 1 in "Consumer Key" and "Consumer Secret," and press "Connect to Kaonavi." When "Connected" appears, you are done.
3. Each person verifies their identity
Each person who will use it presses "Verify my Kaonavi account" once in the Kaonavi settings on the same screen. They are linked to the Kaonavi user with the same email address as their Samurai App account, and operate as the member linked to that user. People who are not registered as users who can sign in, or who have no linked member, cannot use it.
4. Ask in chat
In chat, ask specifically whose sheet to read and what to add. For writes, read the approval card before allowing it.
Things to watch
Anyone who has verified their identity can read the sheets in the operation scope for everyone. Apart from what they can see in Kaonavi's screens, the credential's operation scope is the boundary. Do not put sheets you want to limit to certain people, such as review or interview records, in the operation scope.
A write has not been applied yet at the moment it is accepted. Progress can end in "NG" or "ERROR," so for important updates, check through to the progress.
It is not suited to updating many people at once. Writes from chat cover one person at a time, and Kaonavi allows at most 5 updates per minute per company. Do company-wide bulk updates in Kaonavi's screens or through the official integration methods.
If an employee number changes, verify again. The person in Kaonavi is linked by employee number, so if HR changes it, that person presses "Verify my Kaonavi account" again.
Disconnecting also removes everyone's identity verification. The same happens when you reconnect with a different Consumer Key. Disconnecting in Samurai App does not delete the credential itself, so when you no longer use it, delete it in Kaonavi's admin functions.
Frequently asked questions
Can I keep the AI from reading review or interview sheets?
Yes. If you turn that sheet off in the operation scope of the Kaonavi credential, Samurai App cannot read it. It does not appear in the list of readable sheets either.
Can it read gender or date of birth?
No. Even if Kaonavi returns them, Samurai App does not pass them to chat. It cannot write them in registrations or updates either.
Can I fix earlier records in a multiple-record sheet?
Not from chat. You can add records, but correcting an existing record would replace all of that member's records, so it refuses. Make corrections in Kaonavi's screens.
We also use SmartHR. Can we connect both?
Yes. Add Kaonavi from the "API integrations" tab and SmartHR from the "Connectors" tab.
When connecting, I see "Kaonavi did not accept the credentials"
Check the Consumer Key and Consumer Secret values, and whether fetching "User information" is turned on in the operation scope.
Sources
- kaonavi API v2 (Kaonavi public API documentation)
- System integration (Kaonavi)
- Connecting to external services (Samurai App guide)
- How to connect each API integration service (Samurai App guide)
Based on Kaonavi's public API documentation and official site as of November 9, 2026.