# Keep another system in step with the HR record

> Keep another system in step with the HR record: 0 companies fully do it, 8 with a limit, 12 carry the tag. Every listing in HR & employee operations with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/hr.sync-people/
- Markdown: https://www.anchorterminal.com/niches/hr.sync-people/index.md (~1,150 tokens)
- Slim: https://www.anchorterminal.com/niches/hr.sync-people/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/hr.sync-people/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 8 | 12 | 22 | 5 |

## What counts as done

A full employee list paged to completion, then an event for each hire, change and termination, each carrying the employee id and the changed fields.

Measured, for our own tests: each event arrives within 15 minutes.

How agents ask for it: sync new hires to our ops app; deprovision leavers; pull headcount into the dashboard; keep the directory in the warehouse current

## Does the job, with a limit

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.

- **BambooHR (Bamboo HR LLC)**: List employees pages to completion, and webhooks fire employee.created, .updated and .deleted with monitorFields naming the changed fields; GET /employees/changed covers gaps. No time-off decision event and no delivery latency are documented.
- **Deel (Deel, Inc.)**: GET /people pages the whole directory with offset and limit, and webhooks deliver platform events with a simulate endpoint for testing. The event type list sits behind GET /webhooks/events/types and was not read, so hire, change and termination events with changed fields are unconfirmed.
- **Factorial (Everyday Software, S.L.)**: Employees page with limit and a cursor, and webhooks fire employees/employee/create_with_contract, /update, /terminate and timeoff/leave/approve and /reject with the row as payload. Delivery latency is not stated.
- **HiBob (Hi Bob Ltd.)**: Webhooks send employee.created, .updated, .joined, .left and time off events, signed, and people search returns everyone at once. A lasting partner account needs Marketplace certification: acc-07's test accounts expire after six months.
- **Humaans (Humaans Software UK Ltd)**: People page to completion, and webhooks fire person.created, person.updated, person.offboarded, person.deleted, jobRole and compensation events and timeAway.approved and .rejected. Whether payloads list the changed fields and delivery latency are not stated.
- **Remote (Remote Europe Holding B.V.)**: Employments page to completion, and webhooks cover employment.onboarding.started and .completed, employment.details.updated, employment.status.updated, offboarding events and timeoff.requested, .approved and .declined, with replay. Changed-field lists and latency were not read.
- **Rippling (People Center, Inc. dba Rippling)**: List workers pages with cursor and next_link, and the Worker Changes API is a feed of hires, field updates, scheduled changes and offboardings with field keys, polled by applied_on. It is a poll rather than a pushed event, so the 15-minute bar depends on the agent's polling.
- **Zoho People (Zoho Corporation Private Limited)**: Form records page up to 200 a call, so a full list is a sequence of reads and change detection is a poll. No webhook endpoint appears in the API index, so hires, changes and leavers raise no event through the API.

## What stops agents finishing

- partner or marketplace approval needed for a lasting API account (HiBob)
- no event for a change, so the agent re-reads the whole directory

## Around it

Before: hr.onboard-hire. After: agent-auth.provision-account, data.load.

## Where this comes from

Weight 22 of 100 in HR & employee operations: 5 of 13 accounts (employee sync with webhooks, SCIM provisioning, a Deel dashboard, unified HRIS APIs, HiBob people sync); set by hand

As data: https://www.anchorterminal.com/api/v1/use-cases/hr.sync-people.json, or the MCP tool get_use_case with id hr.sync-people. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
