Connect Linear and Pipedrive
Start a client’s workflow in Linear and act in Pipedrive, or the other way round, on the client’s own accounts.
Each app by itself: Linear integration and Pipedrive integration, with how to connect it, its scopes and its limits.
What the pair is used for
- A team that logs change requests as Linear issues can open a Pipedrive deal for each new issue in a team, titled from the issue.
- When a Pipedrive deal is won, Linear can open an issue in the team you name, titled with the deal, so the build work is on the board as soon as the sale closes.
- A scheduled Pipedrive call or meeting can become a Linear issue named after its subject, and a new person in Pipedrive can become one named after them.
Every way Linear and Pipedrive join
A workflow starts from a trigger in one app and runs a step in the other, on the client’s accounts. Where the library has a starter for it, it installs that pairing into a client switched off; any other pairing is two steps on the canvas.
From Linear to Pipedrive
| When this happens in Linear | This runs in Pipedrive | How fast | Starter |
|---|---|---|---|
| An issue is opened | List people | Within seconds | Two steps on the canvas |
| An issue is opened | Create a person | Within seconds | Two steps on the canvas |
| An issue is opened | Update a person | Within seconds | Two steps on the canvas |
| An issue is opened | Create a deal | Within seconds | Install the starter |
| An issue changes status | List people | Within seconds | Two steps on the canvas |
| An issue changes status | Create a person | Within seconds | Two steps on the canvas |
| An issue changes status | Update a person | Within seconds | Two steps on the canvas |
| An issue changes status | Create a deal | Within seconds | Install the starter |
From Pipedrive to Linear
| When this happens in Pipedrive | This runs in Linear | How fast | Starter |
|---|---|---|---|
| A deal moves to a stage | Create an issue | Within seconds | Install the starter |
| A deal moves to a stage | Update an issue | Within seconds | Two steps on the canvas |
| A deal is won | Create an issue | Within seconds | Install the starter |
| A deal is won | Update an issue | Within seconds | Two steps on the canvas |
| A new deal is created | Create an issue | Within seconds | Install the starter |
| A new deal is created | Update an issue | Within seconds | Two steps on the canvas |
| A new contact is added | Create an issue | Within seconds | Install the starter |
| A new contact is added | Update an issue | Within seconds | Two steps on the canvas |
| An activity is scheduled | Create an issue | Within seconds | Install the starter |
| An activity is scheduled | Update an issue | Within seconds | Two steps on the canvas |
Set up the starter
Create a deal in Pipedrive when an issue is opened in Linear
- 1Install the starter into the client from Templates → Library. It lands switched off.
- 2Connect the client’s Linear, for “An issue is opened”
- 3Connect the client’s Pipedrive, for “Create a deal”
- 4Fill in Linear: Team ID (Webhooks can be made only with an admin’s API key)
- 5Switch it on. Within seconds: Linear tells us as it happens.
What it produces
The Pipedrive step as it runs for an example client, Lakeview Consulting, when Emma Collins asks for a consultation: each value the starter fills in.
- Title
- Emma Collins
Setup notes for this pair
- The “An issue changes status” starter opens a deal on every status move, so one issue can make several deals. “An issue is opened” makes one per issue.
- The “Linear: Team ID” field does both jobs. It picks the team whose issues open deals and the team that receives issues from Pipedrive.
Field mapping, starter by starter
Each value a starter’s step is given, and where it comes from. Words in brackets are filled in when it runs; change any of it after installing.
Create a deal for new issues
Create a deal in Pipedrive when an issue is opened in Linear
| Pipedrive value | Filled from |
|---|---|
| Title | [the issue’s title, from Linear] |
Create a deal for issue status changes
Create a deal in Pipedrive when an issue changes status in Linear
| Pipedrive value | Filled from |
|---|---|
| Title | [the issue’s title, from Linear] |
Create an issue for scheduled activities
Create an issue in Linear when an activity is scheduled in Pipedrive
| Linear value | Filled from |
|---|---|
| Team ID | [Linear: Team ID] |
| Title | [the activity’s subject, from Pipedrive] |
Create an issue for new deals
Create an issue in Linear when a new deal is created in Pipedrive
| Linear value | Filled from |
|---|---|
| Team ID | [Linear: Team ID] |
| Title | [the deal’s title, from Pipedrive] |
Create an issue for deal stage moves
Create an issue in Linear when a deal moves to a stage in Pipedrive
| Linear value | Filled from |
|---|---|
| Team ID | [Linear: Team ID] |
| Title | [the deal’s title, from Pipedrive] |
Create an issue for won deals
Create an issue in Linear when a deal is won in Pipedrive
| Linear value | Filled from |
|---|---|
| Team ID | [Linear: Team ID] |
| Title | [the deal’s title, from Pipedrive] |
Create an issue for new contacts
Create an issue in Linear when a new contact is added in Pipedrive
| Linear value | Filled from |
|---|---|
| Team ID | [Linear: Team ID] |
| Title | [the contact’s name, from Pipedrive] |
Linear and Pipedrive and their logos are trademarks of their owners, used here only to say what Thrum works with; no endorsement is implied.
Thrum is cooking.
Get early access and you’ll be among the first in. Early members get a launch perk.