Updated: August 2026
Quick Answer. Of the eight HR platforms most common in India, only Darwinbox writes employee data into Google Workspace user profiles, and that connector is listed as paid. Keka, greytHR, Zoho People, HROne, Pocket HRMS, sumHR and Kredily do not. Among global platforms, Deel, Rippling and HiBob provision natively. Google Workspace accepts synced attributes only from Microsoft Active Directory, Entra ID or LDAP, so no HR system is a supported source.
Related guides: Keka email signatures, greytHR email signatures, Zoho People email signatures, and automate signatures from employee data.
The short answer
Almost none of them. Of the eight HR platforms most common in India, exactly one writes employee data into Google Workspace user profiles, and that connector is listed as paid. The global platforms do better, because they sell to IT as well as HR.
This matters for anything downstream of your directory: email signatures, contact cards, org charts, access reviews. If HR is the only system that knows someone changed roles, everything that reads the directory is quietly wrong.
Centralize your team's email signatures in 7 days.
SyncSignature deploys signatures across Google Workspace and Microsoft 365 with directory sync. Teams plan from $2/user/mo (5-seat min). 7-day trial, no credit card.
The comparison table
Checked in August 2026, against each vendor's own documentation, the Google Workspace Marketplace, and the Microsoft Entra application gallery.
HR platform | Creates users in Google Workspace | Writes job title and department into Google Workspace | Syncs to Microsoft Entra ID | API access |
|---|---|---|---|---|
Keka | No | No | Yes, adds, updates and deletes employee records in Entra | Add-on, enabled by your account manager, price not published |
greytHR | Not documented | Not documented | Not documented | Paid add-on, published at Rs 15 per employee per month, included on Premium |
Darwinbox | Yes, its G Suite Admin connector creates, updates and removes user profiles, listed as paid | Yes | Yes, provisioning and deprovisioning | Access on request |
Zoho People | No, the sync runs the other way, Google into Zoho People | No | No | Included on all plans with published rate limits |
HROne | Not documented | Not documented | Not documented | Public docs, not listed in the plan table |
Pocket HRMS | Not documented | Not documented | Not documented | API and webhooks listed as a Premium tier feature |
sumHR | Not documented | Not documented | Not documented | No public API documentation found |
Kredily | Not documented | Not documented | Not documented | No public REST API documentation found |
BambooHR | No native path, commonly done with paid middleware | Not natively | Not natively | Public docs, no add-on fee found |
Deel | Yes | Yes, its field mapping names job title and department | Yes | Public docs |
Rippling | Yes | Yes, attribute push on a cadence you set | Yes | Public docs |
HiBob | Yes | Yes | Yes | Public docs |
What not documented means. We checked the vendor's own integrations page, the Google Workspace Marketplace, and the Microsoft Entra application gallery, and found nothing. That is not proof a capability is absent. It does mean a buyer cannot find it, which amounts to the same thing on a Tuesday afternoon.
The pattern worth noticing
Where HR platforms do write to a directory, they write to Microsoft. Keka provisions into Entra ID and does nothing for Google. Darwinbox provisions into both but its Google connector carries a separate paid tag. The Indian platforms below those two do not provision to either.
There is a structural reason the Google side is worse, and it is not the HR vendors' fault. Google Workspace accepts synced employee attributes only from Microsoft Active Directory, Microsoft Entra ID, or LDAP. HR systems are not a supported source. So even a vendor that wanted to build the Google path has to build it as a direct API integration rather than plug into something Google already supports.
The most instructive example is Zoho, because Zoho owns both halves. Zoho People, the HR product, syncs users in from Google Workspace and its Marketplace listing asks only for read access to directory information. Zoho Directory, a different product, does full create and update into Google Workspace with field mapping. Even the vendor that has an HRIS and a directory under one roof keeps the writing in the directory product.
What this costs you in practice
Three things break, in roughly this order.
Job titles go stale. Someone is promoted in March. HR knows. The directory does not. Every email they send for the next year carries the old title.
Leavers linger. HR records the exit date. If nothing carries that into the directory on the day, the account and everything attached to it stays live until someone remembers.
Somebody maintains it by hand. Usually an ops or IT person, usually in the Google Admin console, usually one user at a time. Admins who get tired of it end up in command line tooling, running bulk title updates through GAM.
Your three options if your HR platform does not write to your directory
Pay for API access and build the bridge. Most workable if your platform's API is included, most annoying if it is a per-employee add-on. You are also signing up to own the field mapping and the breakage.
Export on a schedule. Most HR platforms will email or SFTP a scheduled employee report without any API. It is not elegant and it is often the fastest thing that works.
Skip the directory for the things that do not need it. Email signatures are the clearest case. A signature tool that reads your HR system directly does not care whether Google Workspace ever learns anyone's job title. SyncSignature reads Google Workspace and Microsoft 365 directories, and reads Keka directly through its API.
Frequently asked questions
Can Google Workspace pull job titles from an HR system?
No. Google Workspace Directory Sync supports Microsoft Active Directory, Microsoft Entra ID, and LDAP as sources. An HR platform is not a supported source, so there is no native path from an HRIS to a Google Workspace user profile.
Which Indian HR platform syncs to Google Workspace?
Darwinbox is the only one in this comparison with a native Google Workspace connector that creates, updates, and removes user profiles, and Darwinbox lists that connector as paid. Keka, greytHR, Zoho People, HROne, Pocket HRMS, sumHR, and Kredily have no documented outbound sync to Google Workspace.
Does SSO count as syncing?
No, and this is the most common mix-up. Single sign-on lets your employees log in to the HR system with their Google or Microsoft account. It moves no employee data in the other direction. Several vendors describe both under one integrations heading, which makes it easy to assume you have a sync you do not have.
Does a missing Marketplace listing prove there is no integration?
No. Deel, Rippling, and HiBob all provision into Google Workspace without a Marketplace listing, using direct admin consent. A missing listing only matters alongside a vendor integrations page that shows nothing either, which is the case for the platforms marked not documented above.
How often is this table updated?
Checked August 2026. We re-verify every cell against vendor documentation twice a year, because integration pages change quietly and old comparisons age badly.
Centralize your team's email signatures in 7 days.
SyncSignature deploys signatures across Google Workspace and Microsoft 365 with directory sync. Teams plan from $2/user/mo (5-seat min). 7-day trial, no credit card.
Share this post