Skip to main content
ProductBrain sits above your delivery tracker. The integration is a signal channel at the job level, not a sync:
  • A new ProductBrain Job creates a Linear parent issue (the work handoff).
  • That issue reaching Done marks the job delivered, dev work complete, proof condition not yet verified. The done state stays reserved for a human (or agent) confirming the proof in the deployed product.
Nothing else crosses the seam. Goals, needs, approaches, and phases stay in ProductBrain. Tickets, sprints, and cycles stay in Linear.

​
What you need

  • ProductBrain Builder or Team plan (API access) and an API key (Settings → API Keys)
  • A Make.com account, free tier is enough
  • A Linear personal API key (Settings → Security & access)

​
Setup

1

Import the blueprints

Download both blueprints from the repo: pb-to-linear and linear-to-pb. In Make: Create a new scenario → ⋯ → Import Blueprint.
2

Create the webhooks

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

Fill the placeholders

Scenario A’s HTTP module: your Linear API key and team ID. Scenario B’s HTTP module: your ProductBrain API key.
4

Point ProductBrain at Make

5

Point Linear at Make

Linear → Settings → API → Webhooks → new webhook with Scenario B’s URL, resource type Issues.
6

Turn both scenarios on

Create a job in ProductBrain, a Linear issue appears. Move it to Done, the job shows delivered.

​
How the linkage works

The Linear issue description carries a marker line:
Scenario B parses it to find the right job. Don’t edit or delete that line.

​
Why delivered, not done?

A closed ticket is a claim that work is finished. A ProductBrain job is a proof condition. Something observable in the deployed product. The integration records the claim (delivered). Verifying the proof and marking done stays with you or your agent. That distinction is the point of the system.