Skip to main content
A new ProductBrain Job creates a Feature work item (PBIs/stories live under it). That container reaching Done or Closed marks the job done. Nothing else crosses the seam.

​
Setup

1

Import the blueprints

From the repo: pb-to-azure-devops and azure-devops-to-pb. In Make: Create a new scenario → ⋯ → Import Blueprint.
2

Create the webhooks

In each scenario, open the first module and create a new custom webhook. Copy both URLs.
3

Fill the placeholders

Scenario A (PB → Azure DevOps): your org/project in the URL and a Basic auth value. base64(:personal-access-token) (note the leading colon. PAT needs Work Items read/write). Scenario B: your ProductBrain API key (Settings → API Keys).
4

Point ProductBrain at Make

5

Point Azure DevOps at Make

Project Settings → Service hooks → Create subscription → Web Hooks → Work item updated, URL = Scenario B’s hook.
6

Turn both scenarios on

Create a job in ProductBrain, Feature work item appears. Complete it, the job shows done.

​
How the linkage works

The Feature’s description carries a marker line:
Scenario B parses it. Don’t edit that line.

​
When does a job become done?

In ProductBrain, done means the work is live in production. The integration marks the job done when its Feature work item reaches Done or Closed, so point the trigger at the state your team uses for shipped work. If your team closes tickets before a release goes out, move the trigger to the status that means released, or jobs will read done early.
Verified with live Make scenarios against payloads in Azure DevOps’ documented service-hook shape. The first run on your org is the final validation.