Connect Notion and Pipedrive
Start a client’s workflow in Notion and act in Pipedrive, or the other way round, on the client’s own accounts.
Each app by itself: Notion integration and Pipedrive integration, with how to connect it, its scopes and its limits.
What the pair is used for
- A Notion database the whole team reads can hold the pipeline. Each new or won Pipedrive deal adds a row titled with the deal, within seconds.
- Scheduled calls and meetings can add rows titled with the activity’s subject, such as “Boiler service”.
- New people in Pipedrive can become rows titled with their name.
Every way Notion 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 Notion to Pipedrive
| When this happens in Notion | This runs in Pipedrive | How fast | Starter |
|---|---|---|---|
| A row is added to a database | List people | Within 15 minutes | Two steps on the canvas |
| A row is added to a database | Create a person | Within 15 minutes | Two steps on the canvas |
| A row is added to a database | Update a person | Within 15 minutes | Two steps on the canvas |
| A row is added to a database | Create a deal | Within 15 minutes | Two steps on the canvas |
| A row is changed | List people | Within 15 minutes | Two steps on the canvas |
| A row is changed | Create a person | Within 15 minutes | Two steps on the canvas |
| A row is changed | Update a person | Within 15 minutes | Two steps on the canvas |
| A row is changed | Create a deal | Within 15 minutes | Two steps on the canvas |
From Pipedrive to Notion
| When this happens in Pipedrive | This runs in Notion | How fast | Starter |
|---|---|---|---|
| A deal moves to a stage | Add a database row | Within seconds | Install the starter |
| A deal moves to a stage | Update a database row | Within seconds | Two steps on the canvas |
| A deal is won | Add a database row | Within seconds | Install the starter |
| A deal is won | Update a database row | Within seconds | Two steps on the canvas |
| A new deal is created | Add a database row | Within seconds | Install the starter |
| A new deal is created | Update a database row | Within seconds | Two steps on the canvas |
| A new contact is added | Add a database row | Within seconds | Install the starter |
| A new contact is added | Update a database row | Within seconds | Two steps on the canvas |
| An activity is scheduled | Add a database row | Within seconds | Install the starter |
| An activity is scheduled | Update a database row | Within seconds | Two steps on the canvas |
Set up the starter
Add a database row in Notion when an activity is scheduled in Pipedrive
- 1Install the starter into the client from Templates → Library. It lands switched off.
- 2Connect the client’s Pipedrive, for “An activity is scheduled”
- 3Connect the client’s Notion, for “Add a database row”
- 4Fill in Notion: Database ID (For example the 32 characters in the database URL)
- 5Fill in Notion: Title column (For example Name)
- 6Switch it on. Within seconds: Pipedrive tells us as it happens.
What it produces
The Notion step as it runs for an example client, Lakeview Consulting, when Emma Collins asks for a consultation: each value the starter fills in.
- Database ID
- appXXXXXXXXXXXXXX
- Title
- Emma Collins
- Title property
- [Notion: Title column]
Setup notes for this pair
- Only the title is set. Name the database’s title column in “Notion: Title column”, and give the other properties defaults in Notion, because this step leaves them to Notion.
- Every event adds a new row, so a deal that is created and later won appears twice. Changing the first row instead takes “Update a database row” and that row’s page id.
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.
Add a database row for scheduled activities
Add a database row in Notion when an activity is scheduled in Pipedrive
| Notion value | Filled from |
|---|---|
| Database ID | [Notion: Database ID] |
| Title | [the activity’s subject, from Pipedrive] |
| Title property | [Notion: Title column] |
Add a database row for new deals
Add a database row in Notion when a new deal is created in Pipedrive
| Notion value | Filled from |
|---|---|
| Database ID | [Notion: Database ID] |
| Title | [the deal’s title, from Pipedrive] |
| Title property | [Notion: Title column] |
Add a database row for deal stage moves
Add a database row in Notion when a deal moves to a stage in Pipedrive
| Notion value | Filled from |
|---|---|
| Database ID | [Notion: Database ID] |
| Title | [the deal’s title, from Pipedrive] |
| Title property | [Notion: Title column] |
Add a database row for won deals
Add a database row in Notion when a deal is won in Pipedrive
| Notion value | Filled from |
|---|---|
| Database ID | [Notion: Database ID] |
| Title | [the deal’s title, from Pipedrive] |
| Title property | [Notion: Title column] |
Add a database row for new contacts
Add a database row in Notion when a new contact is added in Pipedrive
| Notion value | Filled from |
|---|---|
| Database ID | [Notion: Database ID] |
| Title | [the contact’s name, from Pipedrive] |
| Title property | [Notion: Title column] |
Notion 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.