Keka and CultureMonkey, one org chart

Sync employees along with the teams, sub-teams, locations and business units they sit in, so every survey reaches the right people and every report groups them correctly.

Browse all integrations

Book a free, no-obligation product demo call with our experts.

How does the CultureMonkey Keka integration work?

CultureMonkey reads your Keka tenant through its own secure sync service rather than calling Keka from your account directly. That service authenticates with your credentials, reads your data, normalises it, and hands it back to CultureMonkey in a consistent shape. Keka stays the source of truth: edits made to a synced employee inside CultureMonkey can be reverted on the next run.

It is one of the more structural HRIS connectors, because it brings across the groupings your reports are built on and not just the people:

  • Credentials neededKeka API credentials and your Keka subdomain, generated by your Keka administrator, plus an Account Admin in CultureMonkey to own the connection.
  • Who sets it upCustomer Success. Keka is an assisted integration rather than a self-serve form, so credentials are registered and the first sync verified with our team.
  • First syncRuns as soon as authentication succeeds, pulling teams, locations, business units and employees.
  • Ongoing cadenceTwice a week on Tuesday and Friday. Accounts opted into daily sync refresh once a day instead.
  • Off-schedule runsAfter a large reorg you can request a sync rather than waiting for the next scheduled slot.
  • Employee matchingExternal IDs and work email, so records are updated rather than duplicated, including employees you previously loaded by CSV.
How it works

What syncs from Keka, and how often

Type of integration

HRIS employee and org sync

Direction

One-way, read only

Sync cadence

Tuesday and Friday, or daily

Employee matching

External ID and work email

Full setup guide: Connect Keka

Key capabilities

Org data accurate enough to report on

Your org data decides who receives a survey, how results are grouped, which manager sees which dashboard, and where anonymity thresholds fall. Keeping it in step with Keka is what makes all four trustworthy.

Your org structure, not just your people

Teams, sub-teams, locations and business units come across alongside employees, so the segments you slice engagement survey results by match how Keka is actually organised.

  • Teams and sub-teams arrive together, with sub-teams mapped from Keka's project team structure.
  • Locations and business units land as their own groupings, ready to filter on.
  • Each group matches on an external ID, so renaming a team in Keka updates the existing group in your reports rather than creating a duplicate.

A wide set of employee fields, mapped by default

Keka's default mapping covers a wide set of fields, and the common ones map automatically. Anything else can go onto a custom attribute for feedback segmentation.

  • Identity and role: name, work email, employee ID and designation.
  • Dates that power tenure segments and lifecycle surveys: joining, separation and date of birth.
  • Demographics and status: gender, job status and an active flag that drops leavers out of future sends, keeping anonymous feedback audiences clean.

Reporting lines resolved in a second pass

Because a manager is also an employee, the integration loads everyone first and then wires up the hierarchy, so manager dashboards settle correctly even when a manager and their report arrive in the same run.

  • Each employee's reporting manager comes across from Keka.
  • A brand-new manager and their report can arrive together and still resolve once the run completes.
  • Clean hierarchy is what makes rolled-up reporting and anonymity thresholds trustworthy at larger headcounts.
Connector or CSV

A live connector versus a CSV import

Both get your people into CultureMonkey. The difference is what happens after the first load.

Live HRIS connectorCSV import
SetupConnect and map fields onceNone, but you rebuild the file each time
Staying currentAutomatic, on a scheduleOnly as fresh as your last upload
New hires and exitsFlow through on the next syncYou remember to re-upload
Effort over timeNear-zero once connectedRecurring, every change
Best forOrganizations on a supported HRISOne-time loads, or unsupported systems
Recognition & compliance

Built for enterprise security, recognized for performance

Security & compliance
AICPA SOC compliance badgeGDPR compliance badgeISO 27001 compliance badge
Rated 4.7/5 on G2
G2 High Performer Enterprise badgeG2 Momentum Leader badgeG2 Fastest Implementation badge
Explore more

Connect the rest of your stack

BambooHRScheduled directory sync with teams, locations and reporting lines.DarwinboxScheduled employee sync with nested team structure and reporting hierarchy.WorkdayImport employees and profile information into CultureMonkey.Security and complianceSOC 2, ISO 27001 and GDPR posture, and how employee data is handled.
FAQ

Frequently asked questions

How often does the Keka integration sync?

Twice a week by default, on Tuesday and Friday. Accounts opted into daily employee sync refresh once a day instead. Beyond the scheduled runs, the first sync happens right after the connection is provisioned, and an off-schedule refresh can be requested after something like a large reorg rather than waiting for the next slot.

Can I connect Keka myself from the Integrations page?

No. Keka is provisioned as an assisted integration rather than a self-serve flow, so the credentials are registered with our team. Start by contacting your Customer Success representative or using the in-product Contact us option on the integration. Once it is live, it appears in your Integrations list.

What does the Keka integration need to connect?

Keka API credentials generated in your Keka admin settings, your Keka subdomain so the sync service knows which tenant to read, and an Account Admin in CultureMonkey to own the connection. Share the credentials only through a secure channel, and rotate them in Keka if you suspect they have been exposed.

Does the sync bring across my org structure or only people?

Both. Alongside employees it syncs teams, sub-teams, locations and business units, which are the groupings your reports and dashboards are built on. Each is matched by an external ID from Keka, so renaming a team updates the existing group instead of creating a duplicate.

Will connecting Keka create duplicate employees?

No. The integration matches on external IDs and email, so it updates existing records rather than duplicating them. If you previously imported employees by CSV, matching reconciles those existing records to their Keka counterparts.

How quickly will a new hire in Keka appear in CultureMonkey?

By the next scheduled sync. On the default cadence that is the following Tuesday or Friday; on the daily cadence it is within a day. If you need someone sooner you can add them manually or request an off-schedule sync.

What happens to an employee when they leave in Keka?

On the next sync they are marked inactive in CultureMonkey with their separation date carried across, and they drop out of future survey sends. Their historical, anonymised responses remain part of past reports.

Can I still edit employees in CultureMonkey once Keka is connected?

You can, but the integration treats Keka as authoritative, so editing a synced employee's team, manager or profile inside CultureMonkey can be reverted on the next run. Make those changes in Keka instead.
Get started

See the Keka sync running on your own directory

Book a free, no-obligation product demo call with our experts.