HR & People Integration

CMap + BrightHR

BrightHR is where your people list lives.
CMap keeps up with it automatically.
One Zapier template, no development work.

Book a demo

What syncs

What the integrations does

Your people list, kept in step.

Most firms end up maintaining the same list of people in two places. This integration removes the second one: add the employee in BrightHR, and CMap follows on its own.

CMap

→

BrightHR

CMap

↔

BrightHR

→

CMap

Employees arrive as users

Adding an employee in BrightHR creates the matching user in CMap, so your CMap people list grows with your headcount rather than trailing behind it.

CMap

↔

BrightHR

→

CMap

→

BrightHR

Full user details

Name, work email, job title and start date are carried across, so the new user is complete enough to resource and to invite into CMap.

CMap

↔

BrightHR

→

CMap

→

BrightHR

Office and team mapped

Your BrightHR site and department values map to CMap offices and teams, so users sit in the right part of the business from the moment they exist.

Why it matters

One people list to maintain.

Every manual copy of your employee list is a chance for the two systems to drift apart. This keeps CMap in line with BrightHR by default.

One place to add a person

HR owns the people record in BrightHR. 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.

Fewer gaps to chase

Missing users are a common cause of unassigned time and half-finished resource plans. This removes the cause rather than the symptom.

Under your control

The workflow lives in your Zapier account. Change the mapping, add conditions, or pause it whenever you need to.

getting set up

Live in an afternoon.

CMap publishes the template, so there is nothing to build. Connect BrightHR and CMap in Zapier, confirm how the fields line up, and switch it on. It is a supported Zapier integration, published and maintained by CMap, so your IT team does not need to be involved.

Book a demo

Connect your accounts

Authorise BrightHR and CMap in Zapier.

Open the CMap template

Start from “Add new BrightHR employees to CMap as users”.

Test and turn on

Run it against one employee, check the user, go live.

Frequently asked questions

Which fields are carried across?

Name, work email, job title and start date, plus the office and team values you choose to map. Any other field on CMap’s Create User step can be mapped once your two accounts are connected in Zapier.

Is the sync two-way?

No. Data moves from BrightHR into CMap only. BrightHR remains the place you edit people records, and nothing is written back into it.

Does the BrightHR 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 Zapier’s plan limits apply to conditions and additional steps.

Does CMap integrate with BrightHR?

Yes, through Zapier. CMap publishes a ready-made template called "Add new BrightHR employees to CMap as users". Adding an employee in BrightHR creates the matching user in CMap. The workflow runs in your own Zapier account.

Could it create duplicate users in CMap?

It can. There is no matching step, so the workflow always attempts to create. A work email address already in use by a CMap user makes the run fail, which you can then correct, but a different address produces a second user for the same person. Import your current employees into CMap before you turn it on, and add a Zapier condition if you only want part of your workforce included.

Are later changes in BrightHR picked up?

No. The workflow runs once, at the point the employee is added. Changes made afterwards, and leavers, are handled separately.

integrations

CMap, embedded in your wider tech stack

BrightHR 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