Niches · HR & employee operations
Update an employee's details
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
The field changed with the effective date, the change attributed to the agent's token in the audit log, and sensitive fields (pay, bank) refused unless the user may edit them, in one call.
How agents ask for it: change my address
, update Kim's job title
, record the pay rise from April
, fix the start date
Does the job, with a limit 8
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| BambooHR C Bamboo HR LLC | POST /employees/{id} updates fields, and table rows (job, compensation) carry effective dates through the table endpoints. Whether the audit log names the token or app for API edits was not found. source |
| Deel BB Deel, Inc. | PATCH /people/{id}/personal and the address and department endpoints change one area per call with an Idempotency-Key. No effective date on these writes or audit log naming the token was found. source |
| Factorial B Everyday Software, S.L. | Updates an Employee changes profile fields and compensation records carry their own dates; whether the audit log names the token for API edits was not found, and an API key grants every scope. source |
| HiBob D Hi Bob Ltd. | PUT /people/{identifier} updates specific fields under field-level permissions, so blocked fields are refused for the service user. Effective dating of table entries and the audit actor for API edits were not read. source |
| Humaans D Humaans Software UK Ltd | PATCH /api/people/:id updates profile fields and compensations carry an effectiveDate, with compensation writes needing their own compensations:write scope. No audit log naming the token was found in the reference. source |
| Remote BB Remote Europe Holding B.V. | PATCH /v2/employments/{id} and the personal, address and bank detail endpoints update one area per call, with contract changes tracked as pending changes. No audit log naming the token was found, and no idempotency key exists. source |
| Rippling B People Center, Inc. dba Rippling | Worker changes record effective_on and applied_on, but no write endpoint for an existing worker's fields is in the v2 reference list read, so updates go through the product or draft flows. source |
| Zoho People D Zoho Corporation Private Limited | Form records can be updated with inputData by label name, one call. No effective-date parameter for employee field changes or audit log naming the token was found in the pages read. source |
What stops agents finishing
- edits to pay need a second approver the agent cannot be
Around it
Before: hr.directory-lookup. After: hr.sync-people.
Where this comes from
Weight 7 of 100 in HR & employee operations: no first-hand account; vendor docs only (Deel personal information, Humaans job roles and compensation); smallest share
The same as data: /api/v1/use-cases/hr.update-record.json, or the MCP tool get_use_case with id hr.update-record. Other jobs in this category: /api/v1/niches?category=hr.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.