Resource Management

CMap + Float

Connect delivery planning in CMap with resource scheduling in Float.
Clients, projects and time off flow between the two through ready-made Zapier templates,
so your Float schedule reflects what is happening in CMap without anyone re-keying it.

Book a demo

What syncs

What the integrations does

Clients and projects out. Availability back.

The records you manage in CMap create and update the matching records in Float through ready-made Zapier templates, and new clients and time off flow back to CMap.

CMap

→

Float

CMap

↔

Float

→

CMap

New clients and projects

New companies become Float clients and new projects are created in Float, so resourcing can start as soon as work is won.

CMap

↔

Float

→

CMap

→

Float

Projects stay current

When a project changes in CMap, the matching Float project, found by project code, is updated, so the schedule reflects the latest stage, dates and status.

CMap

↔

Float

→

CMap

→

Float

Clients and time off

New Float clients become CMap companies, and time off booked in Float is recorded as holidays against the right CMap user.

Why it matters

One plan, feeding your schedule.

CMap plans the work and Float schedules the people. This integration keeps the two aligned so nobody re-keys anything.

One plan, one schedule

Delivery decisions made in CMap show up in Float automatically, so planners always work from current information.

No re-keying

Clients, projects and time off are created once and flow to the other system, never typed twice.

Faster to resource

A won project lands in Float ready to staff, so scheduling can start the day it is created.

Accurate availability

Time off booked in Float is reflected in CMap, so capacity and holidays line up.

getting set up

Set up in your own Zapier account.

You run the flows in Zapier using CMap's ready-made templates. Connect both systems, switch on the templates you need, and align your reference data, then each workflow runs on its own.

Book a demo

Connect your accounts

Turn on the templates you need

Use the CMap Zap templates for the flows that matter: clients, projects, project updates and time off. Each is a handful of steps.

Align your reference data

Match your Float project stages to your CMap sales stages and confirm your people exist in both systems, then test each workflow and switch it on.

Frequently asked questions

Do I need to align anything before going live?

Yes. Your Float project stages should match your CMap sales stages (set in Admin > Content > Dropdown List Options > Sales Stages), and people should exist in both systems so time off can be matched.

How are projects kept in sync?

Projects are matched by project code. When a CMap project is updated, the matching Float project is found by its code and updated, so the codes must be identical in both systems.

Does it need custom fields or an API key?

No. CMap connects with your CMap ID, and Float has no custom fields, so the templates map standard fields only.

What data syncs between CMap and Float?

New companies and clients, new projects, project updates matched on project code, and time off booked in Float recorded as holidays in CMap. Most flows are one way.

Which editions is it available in?

Both the Consulting (PSA) and AEC editions of CMap. There is no additional CMap charge, though a paid Zapier plan is needed because the workflows have more than two steps.

How does the Float integration work?

It is a supported Zapier integration. CMap publishes ready-made Zap templates that you run in your own Zapier account. Each template connects a trigger in one system to an action in the other, such as a new CMap project creating a Float project.

integrations

CMap, embedded in your wider tech stack

Float is one of CMap's resource management integrations, connected through supported Zapier templates, alongside the accounting, CRM and collaboration tools your business already runs on.

View all integrations