Connect Pipedrive and Slack
Start a client’s workflow in Pipedrive and act in Slack, or the other way round, on the client’s own accounts.
Each app by itself: Pipedrive integration and Slack integration, with how to connect it, its scopes and its limits.
What the pair is used for
- Won-deal kickoff for coaches posts to the team’s Slack channel the same minute a Pipedrive deal is won, alongside the kickoff task and the welcome handed to the owner. See it in the library
- The SEO agency pack adds a second Slack flow beside the won-deal kickoff. Each request posted in the requests channel becomes a task, and the reply in the channel says where it went. See it in the library
- For an executive coach, often paid by the client’s employer, the Executive coach pack tells the team in Slack when a Pipedrive deal is won. See it in the library
- New people added in Pipedrive can post to a channel such as #new-leads with their name and label, and scheduled calls can post their subject and due time.
Every way Pipedrive and Slack 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 Pipedrive to Slack
| When this happens in Pipedrive | This runs in Slack | How fast | Starter |
|---|---|---|---|
| A deal moves to a stage | Post a message | Within seconds | Install the starter |
| A deal moves to a stage | Edit a message | Within seconds | Two steps on the canvas |
| A deal is won | Post a message | Within seconds | Install the starter |
| A deal is won | Edit a message | Within seconds | Two steps on the canvas |
| A new deal is created | Post a message | Within seconds | Install the starter |
| A new deal is created | Edit a message | Within seconds | Two steps on the canvas |
| A new contact is added | Post a message | Within seconds | Install the starter |
| A new contact is added | Edit a message | Within seconds | Two steps on the canvas |
| An activity is scheduled | Post a message | Within seconds | Install the starter |
| An activity is scheduled | Edit a message | Within seconds | Two steps on the canvas |
From Slack to Pipedrive
| When this happens in Slack | This runs in Pipedrive | How fast | Starter |
|---|---|---|---|
| A message is posted in a channel | List people | Within 5 minutes | Two steps on the canvas |
| A message is posted in a channel | Create a person | Within 5 minutes | Two steps on the canvas |
| A message is posted in a channel | Update a person | Within 5 minutes | Two steps on the canvas |
| A message is posted in a channel | Create a deal | Within 5 minutes | Two steps on the canvas |
Set up the starter
Post a message in Slack 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 Slack, for “Post a message”
- 4Fill in Slack: Channel (For example #leads or C0123456789)
- 5Switch it on. Within seconds: Pipedrive tells us as it happens.

What it produces
The Slack step as it runs for an example client, Lakeview Consulting, when Emma Collins asks for a consultation: each value the starter fills in.
- Channel
- #new-leads
- Text
- An activity is scheduled in Pipedrive. Subject: Emma Collins Type (call, meeting…): new Due date: 2026-10-21T09:05:00Z Due time: 240 Duration: 240
Setup notes for this pair
- The Slack app has to be invited to the channel named in “Slack: Channel” before the first deal can be posted.
- Slack’s “Edit a message” can keep one line per deal and change it in place as the deal moves, instead of a new post at every stage.
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.
Post a message for scheduled activities
Post a message in Slack when an activity is scheduled in Pipedrive
| Slack value | Filled from |
|---|---|
| Channel | [Slack: Channel] |
| Text | An activity is scheduled in Pipedrive. Subject: [the activity’s subject, from Pipedrive] Type (call, meeting…): [the activity’s type, from Pipedrive] Due date: [the activity’s due date, from Pipedrive] Due time: [the activity’s value, from Pipedrive] Duration: [the activity’s value, from Pipedrive] |
Post a message for new deals
Post a message in Slack when a new deal is created in Pipedrive
| Slack value | Filled from |
|---|---|
| Channel | [Slack: Channel] |
| Text | A new deal is created in Pipedrive. Deal: [the deal’s title, from Pipedrive] Value: [the deal’s value, from Pipedrive] Currency: [the deal’s currency, from Pipedrive] Status (open, won, lost): [the deal’s status, from Pipedrive] Stage ID: [the deal’s stage id, from Pipedrive] |
Post a message for deal stage moves
Post a message in Slack when a deal moves to a stage in Pipedrive
| Slack value | Filled from |
|---|---|
| Channel | [Slack: Channel] |
| Text | A deal moves to a stage in Pipedrive. Deal: [the deal’s title, from Pipedrive] Value: [the deal’s value, from Pipedrive] Currency: [the deal’s currency, from Pipedrive] Status (open, won, lost): [the deal’s status, from Pipedrive] Stage ID: [the deal’s stage id, from Pipedrive] |
Post a message for won deals
Post a message in Slack when a deal is won in Pipedrive
| Slack value | Filled from |
|---|---|
| Channel | [Slack: Channel] |
| Text | A deal is won in Pipedrive. Deal: [the deal’s title, from Pipedrive] Value: [the deal’s value, from Pipedrive] Currency: [the deal’s currency, from Pipedrive] Status (open, won, lost): [the deal’s status, from Pipedrive] Stage ID: [the deal’s stage id, from Pipedrive] |
Post a message for new contacts
Post a message in Slack when a new contact is added in Pipedrive
| Slack value | Filled from |
|---|---|
| Channel | [Slack: Channel] |
| Text | A new contact is added in Pipedrive. Name: [the contact’s name, from Pipedrive] Organisation ID: [the contact’s org id, from Pipedrive] Owner ID: [the contact’s owner id, from Pipedrive] Label: [the contact’s label, from Pipedrive] Added at: [the contact’s add time, from Pipedrive] |
Pipedrive and Slack 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.