Developer Tools Integration

CMap + GitHub

New projects arrive in GitHub as issues, the moment they are created.
Written once in CMap: no re-typing, no briefing email.
Your developers pick the work up from their own backlog.

Book a demo

What syncs

What the integrations does

Scoped in CMap. Tracked in GitHub.

One workflow, running in one direction. The project your team has just created becomes an issue in the repository where the work will actually happen, complete with the brief.

CMap

→

GitHub

CMap

↔

GitHub

→

CMap

Projects become issues

Every new CMap project creates an issue in the repository you nominate. The project title becomes the issue title, and the More Info field becomes the body, so the brief travels with it.

CMap

↔

GitHub

→

CMap

→

GitHub

Landing pre-sorted

Set the assignee, milestone and labels once and every issue arrives where your team expects it, ready to be triaged rather than tidied up first.

CMap

↔

GitHub

→

CMap

→

GitHub

Filtered to fit

Send only the projects that involve development work, route different teams to different repositories, or carry the same trigger on into the rest of your toolchain.

Why it matters

No re-typing. No waiting for the handover.

CMap runs the commercial side of the project; GitHub runs the build. This closes the gap between them so nothing sits in someone's inbox.

Write the brief once

What your team scopes in CMap is what your developers read in GitHub, with nothing copied across by hand.

Work surfaces immediately

The issue exists the moment the project does, so the build can start before the next stand-up rather than after it.

Developers stay in GitHub

Your engineers work from the backlog they already use all day, and still see everything the business has sold.

Yours to shape

Built on Zapier, so you decide which projects qualify, which repository they land in and what else the trigger sets off.

getting set up

Built from a template, live in minutes.

There is no middleware to build and no code to write. Start from CMap's published Zapier template, point it at a repository and turn it on. Repo is the one field you have to choose yourself, so set it before you go live.

Book a demo

Use the CMap template

Copy the published workflow into your own Zapier account.

Connect CMap and GitHub

Authorise both accounts, using a GitHub account with write access.

Choose your repository

Set the repo, check the title and body mapping, then switch it on.

Frequently asked questions

Which CMap editions is the GitHub integration available on?

Both. The workflow works the same way on the AEC edition and the Consulting (PSA) edition, because it is driven by the creation of a project rather than by any edition-specific functionality.

Do I need a Zapier account?

Yes. This is a Zapier integration, so you need a Zapier account on a plan that supports multi-step Zaps. The workflow runs in your own Zapier account, which means you control exactly what syncs and when. The template itself is published and supported by CMap.

Can I choose which projects create GitHub issues?

Yes. On its own the workflow sends every new project. Add a Zapier filter and only the projects you want continue, based on a field such as project type, office, team or sector. If different teams work in different repositories, Zapier paths let one workflow route projects to the right repository.

Does changing a project in CMap update the GitHub issue?

No. The workflow creates the issue and stops. There is no stored link between the project and the issue, so later changes to the project are not reflected on the issue, and closing the issue does not change anything in CMap. If you want a visible connection, add the CMap project reference to the issue title or body when you set the workflow up.

What data flows between CMap and GitHub?

Data flows one way, from CMap to GitHub. A new CMap project creates a GitHub issue carrying the project title and brief, and you can set the repository, assignee, milestone and labels the issue arrives with. Nothing flows back from GitHub into CMap, so issue comments, activity and closures stay in GitHub.

Does CMap integrate with GitHub?

Yes. CMap connects to GitHub through Zapier using a ready-made CMap workflow template. When a new project is created in CMap, a matching issue is created in the GitHub repository you choose, using the project title as the issue title and the project's More Info field as the issue body.

integrations

CMap, embedded in your wider tech stack

GitHub is one of the Zapier workflows CMap publishes and supports, available on both the AEC and Consulting (PSA) editions, alongside the accounting, CRM and collaboration tools your business already runs on.

View all integrations