Integrations · Updated · November 2026
The CultureMonkey Zoho People integration reads employee data from Zoho People on a schedule, twice a week by default or daily if enabled, so surveys and reports use a current employee list. This guide covers what syncs, setup, security and when to add CultureMonkey to Zoho surveys.
Refreshes twice a week by default, or daily where that is enabled. Custom fields map too.
Short answer
How does CultureMonkey integrate with Zoho People?
CultureMonkey connects to Zoho People with API credentials and reads employee profile and reporting data on a schedule, twice a week by default or daily where enabled. Each run adds new joiners, updates team, manager and location changes and deactivates leavers. The sync is read-only, so nothing in Zoho People changes. Zoho People is a self-serve connector in the CultureMonkey Integrations hub.
The CultureMonkey and Zoho People integration is a live HRIS connector. CultureMonkey uses API credentials from Zoho People to read employee profile and reporting data on a schedule, then updates its employee list to match. Changes reach CultureMonkey on the next run, twice a week by default or daily where enabled, and data flows only one way.
| Item | Zoho People connector |
|---|---|
| Type of integration | HRIS employee and org sync |
| Availability | Self-serve, generally available in the CultureMonkey Integrations hub |
| Authentication | API credentials generated in Zoho People |
| Direction | One way: Zoho People to CultureMonkey, read-only |
| Sync cadence | Twice a week by default; daily if enabled for the account |
| Employee matching | Stable employee or external ID first, then work email |
| What it pulls | Employee profile and reporting data |
Source: CultureMonkey Help Center, Connect an HRIS: overview and supported systems
Zoho People is one of several HR systems on the CultureMonkey integrations page.
The Zoho People sync typically carries the employee data CultureMonkey needs to send surveys and build reports: name, work email and employee ID, job title and status, manager, team, location and business unit, and joining and separation dates. An admin maps each Zoho People field to a CultureMonkey attribute once, custom fields included.
| Data in Zoho People | CultureMonkey attribute | What CultureMonkey uses it for |
|---|---|---|
| First name, last name, work email, employee ID | Identity | Sending personal survey links and matching people on every sync |
| Designation and employee type | Role | Filters and report segments |
| Employee status | Active or inactive | Deactivating leavers and removing any admin access they held |
| Reporting manager | Reporting line | The org hierarchy and each manager's dashboard |
| Department or team, sub-team, location, business unit | Organization | Report segments, heatmaps and anonymity groups |
| Date of joining | Joining date | Lifecycle survey triggers such as the Onboarding stage |
| Date of exit | Separation date | The Separation stage, which triggers an exit survey |
| Date of birth, gender, phone number, where Zoho People provides them | Optional demographics | Filters, and SMS or WhatsApp delivery where a phone number exists |
Zoho People names its fields differently from CultureMonkey, so an admin maps each field once. Each CultureMonkey attribute can be mapped only once, and custom fields can be mapped too. Get work email and a unique employee ID right first, because every sync uses them to recognize people.
Source: CultureMonkey Help Center, Configure HRIS field mapping
Joining and separation dates are what drive CultureMonkey’s employee lifecycle surveys.
To connect Zoho People to CultureMonkey, an account admin opens Integrations, selects Zoho People, enters the API credentials generated in Zoho People, maps each Zoho field to a CultureMonkey attribute, runs the initial sync and spot-checks a few records. After that, the sync runs on its schedule unless the credentials or field mapping change.
Make sure every active employee has a unique employee ID, a work email and a reporting manager.
Create the credentials CultureMonkey asks for in Zoho People's admin settings and share them securely with the CultureMonkey account admin.
Open Integrations, find Zoho People and enter the API credentials.
Match each CultureMonkey attribute to its Zoho People field, including custom fields.
Confirm the first pull, then spot-check names, emails, teams and manager lines for a handful of people.
The sync now refreshes on its schedule. Revisit only if credentials expire or Zoho People fields are renamed.
Source: CultureMonkey Help Center, Connect an HRIS: overview and supported systems
Zoho People syncs with CultureMonkey twice a week by default, or once a day for accounts with daily sync enabled. Each run is a scheduled pull, so a change made in Zoho People today shows in CultureMonkey after the next run. New joiners are added, team and manager changes are updated, and people marked inactive in Zoho People are deactivated.
| Change in Zoho People | What happens in CultureMonkey | When it shows |
|---|---|---|
| A new hire is added | The person is added to the employee list | Next scheduled sync |
| A team, location or business unit changes | The employee record is updated | Next scheduled sync |
| A reporting manager changes | The reporting line updates and the org chart rebuilds | The org chart the day after the sync |
| Someone is marked inactive | The person is deactivated and admin access is removed | Next scheduled sync |
| A Zoho People field is renamed | That field stops updating until it is remapped | After an admin remaps it |
| A survey already launched | The survey keeps the hierarchy from its launch day | Never changes for that survey |
hires were recorded by US employers in September 2026, alongside 5.3 million total separations.
Every one of those changes has to reach your survey list before the next cycle.
If you are weighing other ways to move people data, this guide to SFTP vs API for employee survey data compares them.
Source: CultureMonkey Help Center, Connect an HRIS: overview and supported systems
Yes. The Zoho People integration is read-only: CultureMonkey reads data from Zoho People and never writes anything back. The API credentials are stored securely and used only to fetch employee data. Inside CultureMonkey, data is encrypted in transit and at rest, each customer's data is kept separate, and access to results follows roles.
Source: CultureMonkey Help Center, How CultureMonkey secures your data
IT reviewers can find the full security and compliance details on one page.
For the questions to ask any vendor, use this employee survey vendor security checklist.
Zoho People includes eNPS, pulse and engagement surveys with anonymous options, templates and reports, which suits teams that want basic surveys inside their HRIS. Teams add CultureMonkey for lifecycle surveys by stage, surveys in many languages, delivery by SMS, WhatsApp or QR code, benchmarks, heatmaps and action planning on the same Zoho data.
| Need | Zoho People built-in surveys | CultureMonkey with Zoho People data |
|---|---|---|
| eNPS, pulse and engagement surveys | Yes, all three are listed | Yes, plus lifecycle surveys by stage: Onboarding, Adaptation, Growth and Separation |
| Anonymous surveys | Yes, anonymous surveys are listed | Yes, with a dashboard anonymity threshold, five by default and never below three |
| Survey templates and scheduling | Yes, templates, scheduling and periodic reminders are listed | Yes |
| Delivery channels | Answering on the Zoho People mobile app is listed | Email, SMS, WhatsApp, Slack, Microsoft Teams, QR codes and QR-only surveys |
| Languages | Not listed on Zoho's engagement page | 134 languages |
| Comment analysis | Employee sentiment analysis with Zia is listed | Comment Analytics groups open comments into topics |
| Benchmarks | Not listed on Zoho's engagement page | CultureMonkey People Science benchmarks by driver, industry, company size and region |
| Action planning | Not listed on Zoho's engagement page | Actions from feedback, tracked to completion |
Source: Zoho People, Employee Engagement Software, read on November 10, 2026.
Zoho People is enough when
Teams add CultureMonkey when
To compare full platforms, see this guide to employee engagement software.
With Zoho People data in CultureMonkey, HR can trigger lifecycle surveys from joining and separation dates, give each manager a dashboard for their own reporting line, compare results by team, location and business unit in heatmaps, and keep anonymity thresholds accurate, because group sizes come from current records instead of an old spreadsheet.

S06 E08On keeping a listening tool trusted once it reads HR data:
These tools need to be seen not like police tools, but tools that give hints and sentiment to understand the situation of the people. If we show the output and share it transparently with employees, people will trust the tools and the usage of those tools.
Reading a heatmap well takes practice; this guide on how to interpret employee engagement survey results helps.
For employee engagement strategies beyond the integration, see this guide.
If the Zoho People sync stops updating, first check the schedule, since changes appear only after the next run. Then confirm what the last sync changed, check whether the API credentials expired or were reset, look for Zoho fields that were renamed or left unmapped, and check whether a filter excludes employees. The Help Center covers each check.
| What you see | Likely cause | What to do |
|---|---|---|
| A recent change is missing | The next scheduled sync has not run yet | Wait for the next run, or use a CSV import for that one change |
| Nothing updates at all | The API credentials expired or were reset | Generate new credentials in Zoho People and update them in Integrations |
| One field stopped updating | The Zoho People field was renamed or left unmapped | Remap the field in HRIS field mapping |
| Some employees never appear | A filter or employee status excludes them | Check the status and any filter on the connector |
| A record fails with no clear error | A missing work email or employee ID, or a duplicate | Fix the record in Zoho People; it updates on the next run |
Source: CultureMonkey Help Center, HRIS sync is not updating in CultureMonkey
The CultureMonkey Zoho People integration is a live HRIS connector that reads employee profile and reporting data from Zoho People on a schedule, twice a week by default or daily where enabled. It adds new joiners, updates team, manager and location changes, deactivates leavers and never writes anything back to Zoho People.
This guide covered how the integration works, what data syncs and how CultureMonkey uses it, six setup steps, the sync schedule and what changes on each run, read-only access and security, how Zoho People's own surveys compare with CultureMonkey, what HR can do with the synced data, and how to fix a sync that stops updating.
CultureMonkey turns Zoho People data into a listening program that stays current: lifecycle surveys fire from joining and separation dates, every manager gets a dashboard for their own team, heatmaps compare teams and locations, surveys reach people by email, SMS, WhatsApp, Slack, Microsoft Teams or QR code, and actions from feedback are tracked to completion.
Setup for the Zoho People integration is short: an account admin enters the API credentials, maps fields and runs the initial sync in one session. Most of the effort goes into clean data in Zoho People, especially a unique employee ID and work email for everyone. Plan a quick review of sample records before you launch the first survey.
Yes, if daily sync is enabled for your account. The standard schedule for the Zoho People connector is twice a week, and accounts with daily sync get one refresh every day. Ask your CultureMonkey contact to switch it on. For one urgent change, such as a large group of new hires, a CSV import updates those people right away.
Yes. The Zoho People sync reconciles against your existing employee list instead of replacing it, matching people first by a stable employee ID and then by email address. People added by CSV are not wiped out when you connect Zoho People. Many teams start with a CSV import and switch to the live connector once their Zoho data is clean.
No. Employees never need a Zoho People or CultureMonkey login to answer a survey. Each person receives a personal link by email, SMS, WhatsApp, Slack or Microsoft Teams, or scans a QR code, and the survey opens in a browser. This guide to the employee survey portal explains how employees reach and finish their surveys.
CultureMonkey offers Zoho People and Workline as self-serve connectors, while Darwinbox, Keka, Workday, BambooHR and Freshservice are set up with your CultureMonkey contact. The Workday integration page shows how another connector works. Any system without a connector can load employees by CSV, and ADP is on the roadmap.
When Zoho People marks someone inactive, the next sync deactivates that person in CultureMonkey and removes any admin access they held. If the Separation stage is enabled under lifecycle surveys, the separation date can trigger an exit survey for that person. Keep separation dates accurate in Zoho People so the timing stays right.
Yes. During setup you can map Zoho People custom fields to CultureMonkey attributes, and each CultureMonkey attribute can be mapped only once. Custom fields such as a cost center or shift pattern then work as filters and report segments. Get work email and a unique employee ID right first, because the sync uses them to match people.
Turn your Zoho People data into a listening program
Connect once, keep your employee list current and send every survey to the right people at the right time.