How to connect Pipedrive to Slack and verify it works

To connect Pipedrive to Slack, start from Pipedrive’s integrations or marketplace area, authorize the right Slack workspace, choose the channel that should receive alerts, and then pick the Pipedrive events that will trigger messages. After you save the setup, send a first test or make a simple deal change and confirm the notification appears in the channel you expected.

What you need before you start

• A Pipedrive account with permission to manage integrations. In many setups that means an admin or a user allowed to install and configure apps.
• A Slack workspace where you can approve app installations.
• Permission to post into the Slack channel you want to use. If the channel is private, you usually need to be a member and may need a workspace admin to approve the app.
• A clear decision on where notifications should go before you begin. Decide whether you want a public team channel or a private channel.
• A simple test case you can trigger right away, such as moving one deal to the next stage, so you can confirm the integration worked after setup.

If your Pipedrive plan, Slack workspace rules, or app approval process has changed since the last time you checked, confirm the current requirements in the official Pipedrive and Slack admin settings before you start. That avoids getting stuck halfway through the setup.

Connect Pipedrive to Slack

1. Open Pipedrive and go to the area for apps, marketplace integrations, or settings where connected tools are managed.

2. Find the Slack integration and open its setup page.

3. Start the connection from Pipedrive by choosing the option to connect or install Slack.

4. When Slack opens, sign in to the correct Slack account if you are not already signed in.

5. Approve the request to let Pipedrive access your Slack workspace. If Slack asks you to choose a workspace, pick the one where you want the notifications to appear.

6. Choose the Slack channel that should receive the alerts. If the integration offers a channel picker, select the team channel you want to use. If you do not see the channel you expected, make sure the app has permission to post there.

7. Save the connection in Pipedrive and finish any final setup screen Slack shows.

If your Pipedrive interface names the menu slightly differently, use the official integration entry for Slack rather than trying to build a custom connection from scratch. The exact labels can change, but the flow is usually the same: open the Slack app entry in Pipedrive, authorize in Slack, then choose where messages should land.

Choose which Pipedrive updates should reach Slack

After the connection is in place, open the Slack integration settings in Pipedrive and choose the events that should trigger messages. The available choices can vary by plan or integration version, so use the current settings screen as your source of truth.

A common setup is to send a message when a deal changes stage. For example, you might want a Slack post when a deal moves from Qualified to Proposal Sent, because that gives the team a quick signal that sales progress happened.

Typical event choices to look for include:

• Deal created
• Deal stage changed
• Deal won or lost
• Activity created or completed
• Person or organization updated, if the integration offers those triggers

If the integration lets you filter by pipeline, stage, owner, or team, use those filters to keep the messages relevant. For example, you might send only stage-change alerts for one pipeline instead of every pipeline in the account. Keep the list narrow at first so Slack does not fill up faster than your team can use it.

Send a test message and confirm it worked

1. Save the trigger settings in Pipedrive.

2. Create or change a record that matches the rule you just set. The simplest test is usually a deal stage change.

3. Open the Slack channel you selected and look for the notification.

4. Check that the message appears in the right workspace and the right channel.

5. Confirm that the content matches the Pipedrive change you made. The message should show the deal or activity details the integration is configured to send.

6. If the message arrives, keep the setup and use that same action as your first live check for future changes.

A successful test means two things: the notification appears where you expected, and the details in the message match the event you triggered in Pipedrive. If you changed a deal stage and the Slack post names that deal and stage correctly, the connection is live.

If the message does not show up

Start with the most common setup mistakes before you assume the integration is broken.

• Check that you authorized the correct Slack workspace. It is easy to connect the wrong one if you belong to more than one workspace.
• Confirm the channel choice in the integration settings. A private channel, archived channel, or typo in the destination can keep messages out of sight.
• Make sure the Slack app has permission to post in that channel. In Slack, private channels usually need explicit access.
• Recheck the Pipedrive trigger filters. If you set the rule to watch only one pipeline, stage, owner, or activity type, your test action has to match those filters exactly.
• Confirm that you saved the integration after choosing the event. A setup screen that looks complete is not always saved until you click the final save or confirm button.
• Look at the integration status in Pipedrive’s official settings area. If there is a reconnect or reauthorize option, use it after checking the workspace and channel.
• If Slack shows the app was added but no messages appear, try a simple new test in a channel you know is active and accessible, then compare it against the current integration settings.

If the connection still does not send messages after those checks, use the current Pipedrive and Slack admin settings pages to verify whether the app was restricted by workspace policy, channel access, or a changed permission setting. Those are the most likely places where a working setup can stop producing notifications.