Zoho People

Connect AI agents to Zoho People HR. Agents look up and list employees, read and write records on any People form, apply for and list leave, and pull attendance entries for reporting and timesheet automation.

7 actions OAuth available

Zoho People website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A signed offer completes in the applicant tracking system

Get Employee checks whether the new hire already exists, looked up by Employee ID

Add Form Record creates the Employee form record with name, email, department, and designation mapped from the offer

Add Form Record writes the onboarding checklist record on the custom Onboarding form

List Form Records verifies the record landed with every required field populated

The HR manager reviews the created record before downstream systems provision accounts and payroll picks it up

IT and the hiring manager get the confirmed start details in their channel

What This Integration Enables

Zoho People stores everything as forms: the employee directory is a form, leave is a form, and every custom process HR builds is a form. This connector embraces that model instead of hiding it. Alongside dedicated employee, leave, and attendance actions, the generic form reader and writer reach any form in the account, standard or custom, by its link name. That makes FlowRunner agents useful for the HR workflows that are actually yours, not just the ones a vendor predicted. - Sync the employee directory into warehouses, sheets, and downstream systems - Create onboarding records across the Employee form and any custom form in one flow - Apply for leave on an employee's behalf, entering the normal approval workflow in Pending status - Surface pending leave to approving managers where they already work - Pull attendance entries per employee and date for timesheet and payroll automation HR automation has a specific failure mode: tools that automate the standard objects and abandon you at the first custom process, which in HR is roughly every process. The form model is Zoho People's answer, and FlowRunner's orchestration completes it. Agents read and write the forms your HR team actually built, the approval workflows Zoho People already enforces stay in force, and FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate adds a review layer on the writes that feed payroll and provisioning. The result is automation shaped like your HR processes, not automation your HR processes had to reshape themselves around.

Without FlowRunner

Onboarding is re-keying The same new-hire details get typed into the ATS, the HRIS, and three spreadsheets

Leave state is tribal knowledge Who is out next week lives in an approval queue nobody outside HR can see

Attendance data stays locked in reports Timesheet reconciliation means exporting from Zoho People and massaging CSVs

With FlowRunner

One record, written once Hire data flows from the ATS into the Employee form and custom forms without retyping

Leave visibility where teams plan Pending and approved leave flows to managers, staffing sheets, and capacity plans

Attendance feeds automation directly Check-in and check-out entries pull straight into payroll prep and anomaly checks

Use Case Scenarios

Onboarding that starts the moment the offer is signed

A hire completes in [Greenhouse](/integrations/greenhouse). The agent calls Add Form Record on the Employee form with the mapped fields, then a second Add Form Record on the custom Equipment Request form so IT's queue is populated before day one. Get Employee confirms the record and pulls the assigned Employee ID, which the agent hands to the identity and payroll flows. The HR manager approves the record once; every downstream system reads from it instead of from a forwarded email.

The leave queue that finds its approvers

Twice a day an agent calls List Leave and filters for Pending status. Each pending request becomes a direct message in [Slack](/integrations/slack) to the approving manager: employee, leave type, dates, reason. A weekly pass writes approved leave into the team staffing sheet in [Google Sheets](/integrations/google-sheets) so project leads see next month's coverage while planning sprints. Nobody discovers a key engineer's two-week absence from a calendar collision.

Attendance reconciliation before payroll runs

In the three days before payroll cutoff, an agent walks the directory from List Employees and pulls each person's List Attendance entries for the period. It flags the gaps: days with a check-in and no check-out, employees with zero entries who have no approved leave on List Leave. The exceptions go to HR as a short list with evidence attached, instead of HR eyeballing hundreds of clean rows to find six broken ones. Payroll gets corrected inputs, not corrections after the fact.

Human-in-Loop Highlight

Add Form Record writes directly into the system of record for people's employment, and Zoho People forms are where payroll, access provisioning, and compliance reporting get their facts. A record created on the wrong form, or an Employee form entry with a mistyped salary-relevant field, propagates into every system that trusts the HRIS before anyone spots it. Apply Leave carries a different weight: it files a request in a real person's name that their manager will act on, adjusting balances and staffing plans once approved. So FlowRunner flows treat both writes as proposals. The agent assembles the record from the source system, shows the HR manager exactly which form link name it will write to and every field value it will set, and commits only on approval. Reading the directory runs unattended all day. Writing someone's employment record waits for a person who owns the consequences.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

7 actions

Employees

List Employees Retrieves a paginated list of records from the Employee form, with the fields configured on the form: name, email, department, designation, and more. Cursor-based paging handles large directories.
Get Employee Retrieves one employee's full details, looked up by internal record ID or by the human-facing Employee ID. The verification step after onboarding writes and the enrichment step in approval flows.

Forms

List Form Records Reads records from any Zoho People form by its form link name, standard or custom, with pagination and column search. The escape hatch that makes bespoke HR processes automatable.
Add Form Record Adds a record to any form by link name, with field values keyed by the form's column names. The generic writer behind onboarding and custom-process automation, and one of the operations this page's human gate governs.

Leave

List Leave Retrieves leave records with leave type, from and to dates, employee, and approval status. The source for approver notifications, staffing sheets, and attendance cross-checks.
Apply Leave Applies for leave on an employee's behalf with employee ID, leave type, and dates. Created in Pending status and routed through the organization's normal approval workflow, never around it.

Attendance

List Attendance Retrieves check-in and check-out entries for an employee, optionally restricted to a single date. The raw material for timesheet automation and pre-payroll anomaly sweeps.

Frequently Asked Questions

What can FlowRunner do with Zoho People?

FlowRunner agents can run List Employees, Get Employee, and List Form Records in Zoho People, plus 4 more actions.

Does connecting Zoho People to FlowRunner require OAuth?

Yes. Zoho People connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Zoho People trigger a FlowRunner workflow automatically?

Zoho People doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Zoho People

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us