Start free
Per-pair page

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.

Connect Pipedrive to Slack — start free See reverse direction
Trigger app
Pipedrive as the trigger

Workflows fire when something happens in Pipedrive.

See all 8 triggers →
Action app
Slack as the action

Workflows do something in Slack, instantly.

See all 45 actions →
Connect Pipedrive to Slack — start free
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Pipedrive → Slack

When something happens in Pipedrive, do it in Slack.

8 Pipedrive triggers wired to 45 Slack actions. Most-used pairing: Activity Added → Add Reaction.

Slack → Pipedrive

Or fire it the other way around.

13 Slack triggers wired to 7 Pipedrive actions downstream.

See Slack → Pipedrive →
Popular pairings

Common Pipedrive → Slack workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 360 combinations
When activity added in Pipedrive, add reaction in Slack.

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.

When activity added in Pipedrive, raw api request in Slack.

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.

When activity added in Pipedrive, archive channel in Slack.

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.

When activity added in Pipedrive, cancel scheduled message in Slack.

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.

When new deal in Pipedrive, add reaction in Slack.

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.

When new deal in Pipedrive, raw api request in Slack.

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.

When new deal in Pipedrive, archive channel in Slack.

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.

When new deal in Pipedrive, cancel scheduled message in Slack.

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.

When deal lost in Pipedrive, add reaction in Slack.

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.

How it works

Connect Pipedrive and Slack in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize Pipedrive and Slack

    Open TinyCommand, authorize Pipedrive and Slack once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Pipedrive trigger

    Drop the Pipedrive → Activity Added trigger onto the canvas. TinyCommand auto-registers the webhook.

    POST /v1/webhooks/pipedrive.trigger-activity-added
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Slack action

    Drop the Slack → Add Reaction action below it. Map fields from the Pipedrive payload into the Slack inputs.

    slack.add-reaction
  5. 5
    Publish
    Publish and forget

    Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Pipedrive + Slack.

How long does it take to connect Pipedrive and Slack on TinyCommand?
Under two minutes. Authorize Pipedrive and Slack once each, drop the Pipedrive trigger and Slack action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Pipedrive ↔ Slack integration real-time?
Yes. Both Pipedrive and Slack expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.
Can I filter or transform data between Pipedrive and Slack?
Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Slack.
What Pipedrive events can trigger a Slack workflow?
Any of the 8 Pipedrive triggers, including "Activity Added". Each fires in real time when the matching event happens in Pipedrive.
Do I need a paid plan to use Pipedrive with Slack?
No. There's a free tier that covers most Pipedrive+Slack use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want Slack → Pipedrive instead?
Build it the same way, in reverse. There's a dedicated /integrations/slack/with/pipedrive page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Pipedrive.

+
Pipedrive + Gmail
Email
+
Pipedrive + Google Sheets
Spreadsheets & Databases
+
Pipedrive + HubSpot
CRM & Sales
+
Pipedrive + Stripe
Payments
+
Pipedrive + Notion
Productivity
+
Pipedrive + Airtable
Spreadsheets & Databases
Connect Pipedrive to Slack — start free