Human Resources · Integration
ichris
Add ichris to your product for your customers, and give your AI agents governed access to it.
Embed an ichris integration so your customers can bring their own HR records into your product without re-keying them. HR data is sensitive and its access rules are stricter than most systems, so access is scoped per tenant, limited to the fields you map, and every read and write is logged. fastn handles per-customer authorisation and API upkeep, so onboarding another HR tenant is configuration rather than a release on your side.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read employee records and org structure into your product, mapped to their own fields.
Read leave records so your product can schedule around real availability.
Write updates back so details captured in your product reach their HR system of record.
Trigger your product when a person is hired, changes role, or leaves.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads an employee's details and reporting line before answering a question about them.
An agent updates a record within governed permissions, with each write attributed and audited.
An agent reacts to a departure and starts the offboarding steps across connected systems.
Example prompt
Show me the people who changed manager this quarter and which teams they moved into.
Set up ichris in 4 steps
- 01Open the ichris connector from your fastn dashboard.
- 02Have each customer authenticate their own ichris tenant.
- 03Map the employee, leave, and org fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the ichris integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an ichris integration without building it. Your customers connect their own ichris account inside your product and work their employees, employment records and working time there, with no per-customer code on your side.
- Handle the part that actually costs time: HR data is sensitive and its access rules are stricter than most systems. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an ichris update is not your on-call problem.
- One integration serves your product and your agents. The same governed ichris connection powers in-product features and gives AI agents scoped, audited access, so you keep people data current without manual re-entry without wiring it twice.
Used by these teams
Compare with
ADP Workforce Now
Ceridian Dayforce
DeputyOften used alongside
Tools the same teams tend to run next to ichris, across other categories.
Slack
NetSuite
Notion
Boxichris integration FAQ
How do I add an ichris integration to my product?
Enable the ichris connector in your fastn dashboard, then let each customer authenticate their own ichris account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no ichris client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own ichris account?
Yes. Every connection is scoped to the individual customer, so each authorises their own ichris account and only ever sees their own employees, employment records and working time. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this ichris integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads an employee's details and reporting line before answering a question about them.
Who maintains the ichris integration?
fastn does. When ichris changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
How is sensitive ichris employee data handled?
Access is scoped per tenant and limited to the fields you map, credentials are encrypted, and every read and write is logged. You expose only what your product actually needs rather than the whole employee record.
Can joiner, mover and leaver changes be automated?
Yes. Where ichris is where a hire, a role change or a departure is recorded, that change can trigger downstream provisioning or removal across the customer's other connected systems. Where ichris sits downstream of the HR system of record, the same event can be pushed into it so its worker list, schedules and access stay in step, which is where most of the manual effort sits.
What can I build with the ichris integration?
A common starting point: read employee records and org structure into your product, mapped to their own fields. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the ichris integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding ichris does not change your per-connector cost. You can start free with 3 connected accounts.
Add ichris to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.