Delivery & Engineering Integration

CMap + Azure DevOps

New delivery work, on your board the moment the project exists.
Set it up once in CMap: no re-keying, no tickets forgotten.
Built on Zapier, live in minutes.

Book a demo

What syncs

What the integrations does

Set up in CMap. On the board in seconds.

The hand-off that usually waits for someone to remember to raise a ticket happens on its own, the moment the project exists in CMap.

CMap

→

Azure DevOps

CMap

↔

Azure DevOps

→

CMap

Create work items

A new project in CMap creates a work item in the Azure DevOps project you nominate, as the type you choose: Epic, Feature, User Story or Task.

CMap

↔

Azure DevOps

→

CMap

→

Azure DevOps

Carry the brief over

The project title becomes the work item title and the project bio becomes the description, so the team can see what the work is without opening CMap.

CMap

↔

Azure DevOps

→

CMap

→

Azure DevOps

Routed to your board

Optional area, iteration and assignee values put the work item with the right team, in the right sprint, against the right owner as it is created.

Why it matters

Every project on the board, without the chase.

CMap runs the commercials; Azure DevOps runs the engineering. This keeps the hand-off between them automatic.

Delivery starts sooner

Engineering sees new work as soon as it exists in CMap, rather than at the next stand-up or hand-over call.

No double keying

The project name and the brief are typed once, in CMap, and arrive on the board complete.

Nothing slips through

Every new project reaches the board, so work that was sold does not sit unscheduled because a ticket was never raised.

Yours to shape

Filter which projects create work items, change the field mapping, or send different projects to different boards.

getting set up

Live in minutes, not weeks.

The integration is a ready-made CMap workflow template on Zapier, so there is no code to write and no middleware to build. Three steps, then it runs on its own. Create a project in CMap and the work item appears on your board, with the title and brief already filled in.

Book a demo

Connect your accounts

Open the CMap template in Zapier and link your CMap and Azure DevOps accounts.

Pick the destination

Choose the Azure DevOps project and the work item type to create.

Check the mapping

Title and description are pre-mapped. Add a filter if only some projects belong on the board.

Frequently asked questions

What do I need to set it up?

A Zapier account on a plan that supports multi step Zaps, an Azure DevOps account that can create work items in the project you want to write to, and Webhooks access enabled on your CMap account by your CMap consultant. There is no API key to create.

Does the work item update if the project changes in CMap?

No. The workflow creates a work item and stops. Renaming or cancelling the project in CMap does not change the work item, and closing the work item does not change the project. It is a one way hand off rather than a two way sync.

Can I stop every project from reaching the board?

Yes. Add a filter step in Zapier so that only the projects you want create work items, for example by project type, office or team. You can also send different projects to different Azure DevOps projects using separate workflows or Zapier Paths.

Which work item types can it create?

Any type your Azure DevOps process offers, including Epic, Feature, User Story and Task. Most teams create an Epic or a Feature, because a CMap project usually represents a body of work the team then breaks down. The type is fixed per workflow, so run a workflow per type if you need more than one.

What data syncs between CMap and Azure DevOps?

From CMap to Azure DevOps: a work item is created for every new CMap project, with the project title as the work item title and the project bio as the description. You choose the Azure DevOps project and the work item type, and you can optionally set the area, iteration and assignee. The integration runs one way only, so nothing travels back from Azure DevOps to CMap.

Does CMap integrate with Azure DevOps?

Yes. When a project is created in CMap, a work item is created in Azure DevOps automatically, carrying the project title and brief with it. It is delivered as a ready made CMap workflow template on Zapier, so there is no code to write and no middleware to license.

integrations

CMap, embedded in your wider tech stack

Azure DevOps is one of CMap's delivery integrations, built on Zapier so you can shape it around the way your teams actually work, alongside the accounting, CRM and collaboration tools your business already runs on.

View all integrations