Connect Pipedrive to Slack in two minutes.
Real-time triggers from Pipedrive, ready-made actions in Slack. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Pipedrive.
- Activity AddedWebhook
- New DealWebhook
- Deal LostWebhook
- Deal UpdatedWebhook
- Deal WonWebhook
Workflows do something in Slack, instantly.
- Raw API RequestAPI
- Add ReactionAPI
- Archive ChannelAPI
- Cancel Scheduled MessageAPI
- Create CanvasAPI
- Create ChannelAPI
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Pipedrive, do it in Slack.
8 Pipedrive triggers wired to 45 Slack actions. Most-used pairing: Activity Added → Raw API Request.
Or fire it the other way around.
13 Slack triggers wired to 7 Pipedrive actions downstream.
See Slack → Pipedrive →Common Pipedrive → Slack workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a new activity (call, meeting, task, email) is created in Pipedrive. Use to mirror activities into a calendar or to enforce activity-based SLAs.
Fires when a new activity (call, meeting, task, email) is created in Pipedrive. Use to mirror activities into a calendar or to enforce activity-based SLAs.
Fires when a new activity (call, meeting, task, email) is created in Pipedrive. Use to mirror activities into a calendar or to enforce activity-based SLAs.
Fires when a new activity (call, meeting, task, email) is created in Pipedrive. Use to mirror activities into a calendar or to enforce activity-based SLAs.
Fires when a new deal is added in Pipedrive. Used to celebrate new pipeline in Slack, kick off enrichment, or auto-assign the deal owner.
Fires when a new deal is added in Pipedrive. Used to celebrate new pipeline in Slack, kick off enrichment, or auto-assign the deal owner.
Fires when a new deal is added in Pipedrive. Used to celebrate new pipeline in Slack, kick off enrichment, or auto-assign the deal owner.
Fires when a new deal is added in Pipedrive. Used to celebrate new pipeline in Slack, kick off enrichment, or auto-assign the deal owner.
Fires when a deal is marked as lost in Pipedrive. Common use: log the lost-reason, add the contact to a churn-saver sequence, or trigger a manager review for large lost deals.
Connect Pipedrive and Slack in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Pipedrive and Slack
Open Tiny Command, authorize Pipedrive and Slack once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Pipedrive trigger
Drop the Pipedrive → Activity Added trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/pipedrive.trigger-activity-added - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Slack action
Drop the Slack → Raw API Request action below it. Map fields from the Pipedrive payload into the Slack inputs.
slack.api-request - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about Pipedrive + Slack.
How long does it take to connect Pipedrive and Slack on Tiny Command?
Is the Pipedrive ↔ Slack integration real-time?
Can I filter or transform data between Pipedrive and Slack?
What Pipedrive events can trigger a Slack workflow?
Do I need a paid plan to use Pipedrive with Slack?
What if I want Slack → Pipedrive instead?
Other apps that pair well with Pipedrive.
Wire Pipedrive to Slack in 2 minutes.
Free tier available. No credit card. No onboarding call.
