Book a demo
To see exactly how we can help you drive your company in the right direction, book a demo with an expert.
Book a demo
HR & People Integration
CMap + HiBob
HiBob is where your people list lives.
CMap creates it, then keeps up with it.
Two Zapier templates, no development work.
People, resourcing & timesheets
Always up to date
New starters become users
Changes follow automatically
Your custom fields
HiBob, your people list
Your source of truth
What syncs
New HiBob employees, and later changes to them, onto the CMap user
How it runs
Automatically through Zapier, usually within minutes of the change in HiBob
Works with
Your existing HiBob and Zapier accounts. Nothing to install
Included in
Every CMap plan, Consulting & AEC editions
What the integrations does
Your people list, kept in step.
Most firms end up maintaining the same list of people in two places, then spend the rest of the year discovering where the two have drifted apart. This integration removes the second list: add or edit the employee in HiBob, and CMap follows on its own.
CMap
→
HiBob
CMap
↔
HiBob
HiBob
→
CMap
New starters become users
Adding an employee in HiBob creates the matching user in CMap, so a new starter exists before their first day rather than after somebody remembers to raise a request.
CMap
↔
HiBob
HiBob
→
CMap
CMap
→
HiBob
Changes follow automatically
A promotion, a new job title, a corrected start date: edit it in HiBob and the CMap user is updated too, so the two systems stop telling you different things about the same person.
CMap
↔
HiBob
HiBob
→
CMap
CMap
→
HiBob
Your custom fields
Name, work email, job title and start date come across as standard. Anything else your CMap users need can be held as a HiBob custom field and included, so the record arrives complete.
Why it matters
One people list to maintain.
Every manual copy of your employee list is a chance for the two systems to disagree. This keeps CMap in line with HiBob by default, on the way in and from then on.
One place to add a person
HR owns the people record in HiBob. CMap reflects it without a second data entry job for anyone.
No onboarding queue
New starters no longer wait on someone with CMap administrator rights to create their account for them.
Details that stay right
Job titles and start dates drift out of date quietly, then turn up in a report. Updates flow through as they happen instead.
Under your control
The workflows live in your Zapier account. Change the mapping, add conditions, or pause them whenever you need to.
getting set up
Live in an afternoon.
CMap publishes both templates, so there is nothing to build. Connect HiBob and CMap in Zapier, confirm how the fields line up, and switch them on. It is a supported Zapier integration, published and maintained by CMap, so your IT team does not need to be involved.
Connect your accounts
Authorise HiBob and CMap in Zapier.
Open the CMap templates
Start from the create and update templates, then add any custom fields you want.
Test and turn on
Run each one against a single employee, check the user, go live.
Frequently asked questions
Does the HiBob integration cost extra?
There is no extra CMap charge: it is available on every plan, on both the Consulting and AEC editions. You do need your own Zapier account, and because each workflow is more than two steps, a paid Zapier plan applies.
Are later changes in HiBob picked up?
Yes, that is what the second template does. When an employee record is updated in HiBob, the matching CMap user is updated too. The user is found by an exact match on full name, so names need to be identical in both systems, and a name change should be made in CMap first.
Is the sync two-way?
No. Data moves from HiBob into CMap only. HiBob remains the place you edit people records, and nothing is written back into it.
Can it bring across fields that HiBob does not hold as standard?
Yes. Where a field on the CMap user has no standard equivalent in HiBob, create a custom field in HiBob to hold it and include it in the workflow. The setup guide covers how to find your own field IDs and add them.
Which fields are carried across?
Name, work email, job title and start date as standard, plus any HiBob custom field you choose to include. Because HiBob returns only the fields the workflow asks for, adding one of your own custom fields is a matter of adding its field ID during setup.
Does CMap integrate with HiBob?
Yes, through Zapier. CMap publishes two ready-made templates: one that creates a CMap user when an employee is added in HiBob, and one that updates the CMap user when the employee record changes. Both run in your own Zapier account.
integrations
CMap, embedded in your wider tech stack
HiBob is one of the HR and people systems CMap connects to, alongside the accounting, CRM and collaboration tools your teams already use.
View all integrations
