Human Resources · Integration
Zoho People
Add Zoho People to your product for your customers, and give your AI agents governed access to it.
Zoho People is the HR piece of the Zoho suite, so employee records often connect to the same person in their CRM or Desk, and a write here can be visible across their estate. Forms are the underlying abstraction: employees, leave types and attendance are all records in configurable forms, which means a customer can add fields your integration has never seen and mapping is configuration rather than code. Leave policies and approval chains are per organisation and per country, so a leave balance is computed rather than stored flat. Data centres are regional, so the wrong host produces an authentication error rather than a not-found. fastn resolves the region and organisation per customer.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Zoho People organisation so employee records appear in your product.
Read leave and attendance to show availability next to the work your product schedules.
Map each organisation's own custom form fields as configuration rather than code.
React when someone is onboarded or a leave request is approved.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports who is on leave next week and where coverage is thin.
An agent submits a leave request within governed permissions, with the action audited per tenant.
An agent answers a question about an employee record without an export.
Example prompt
Who is on approved leave next week, and which teams lose more than one person?
Set up Zoho People in 4 steps
- 01Enable the Zoho People connector from your fastn dashboard.
- 02Have each customer authorise their own Zoho People account, so calls run under their credentials rather than a shared key.
- 03Decide which employees, employment records and working time your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Zoho People integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Zoho People integration without building it. Your customers connect their own Zoho People 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 a Zoho People update is not your on-call problem.
- One integration serves your product and your agents. The same governed Zoho People 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
BambooHR
RipplingWorks well with
Zoho CRMOften used alongside
Tools the same teams tend to run next to Zoho People, across other categories.
Slack
NetSuite
Notion
BoxZoho People integration FAQ
How do I add a Zoho People integration to my product?
Enable the Zoho People connector in your fastn dashboard, then let each customer authenticate their own Zoho People account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Zoho People client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Zoho People account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Zoho People 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 Zoho People 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 reports who is on leave next week and where coverage is thin.
Who maintains the Zoho People integration?
fastn does. When Zoho People 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 Zoho People 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 Zoho People 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 Zoho People 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 Zoho People integration?
A common starting point: let a customer connect their own Zoho People organisation so employee records appear in your product. 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 Zoho People integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Zoho People does not change your per-connector cost. You can start free with 3 connected accounts.
Add Zoho People to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.