How to Send Pipedrive Deal Stage Alerts to Slack with Pipedream

pipedream.com > Workflows > + New

Create a new Workflow in Pipedream

Go to pipedream.com and sign in. Click 'Workflows' in the left sidebar, then click the blue '+ New' button in the top right. A blank workflow canvas opens with a trigger slot at the top labeled 'Add a trigger'. You'll configure Pipedrive as the event source here.

1. 1Click 'Workflows' in the left nav
2. 2Click the blue '+ New' button in the top right
3. 3Click the 'Add a trigger' block on the canvas

Trigger Panel > Search > Pipedrive > Deal Stage Changed

Select the Pipedrive trigger

In the trigger search panel, type 'Pipedrive' and select it from the results. Pipedream will show a list of available Pipedrive trigger types. Select 'Deal Stage Changed' — this fires a webhook payload from Pipedrive every time a deal's stage_id changes. Do not select 'New Deal' or 'Deal Updated'; those fire on too many events.

1. 1Type 'Pipedrive' in the trigger search box
2. 2Click 'Pipedrive' in the results
3. 3Scroll to find and click 'Deal Stage Changed'
4. 4Click 'Connect Pipedrive Account' if no account is linked yet

Pipedrive > Settings > Tools and Apps > Webhooks > + Add Webhook

Register the Pipedream webhook in Pipedrive

Copy the webhook URL shown in your Pipedream trigger block. Open Pipedrive in a new tab, go to Settings > Tools and Apps > Webhooks, and click '+ Add webhook'. Paste the Pipedream URL into the Endpoint URL field. Set the Action to 'Updated' and Object to 'Deal'. Save it. Pipedrive will send a test ping immediately.

1. 1Copy the webhook URL from the Pipedream trigger block
2. 2In Pipedrive, navigate to Settings > Tools and Apps > Webhooks
3. 3Click '+ Add webhook'
4. 4Paste the URL, set Action to 'Updated', Object to 'Deal'
5. 5Click 'Save'

Workflow Canvas > Trigger Block > Test > Event Inspector

Inspect the incoming Pipedrive payload

Click 'Test' on your trigger block to load a sample event. Pipedream shows the full JSON payload in the right panel. Find the key fields you'll need: current.stage_id, current.title, current.value, current.currency, current.owner_id, previous.stage_id, and meta.change_source. Expand each object to confirm the values look correct. You'll reference these paths in the next steps.

1. 1Click the 'Test' button on the trigger block
2. 2Click a recent event in the 'Recent Events' panel
3. 3Expand the 'current' object in the event inspector
4. 4Note the exact key paths for stage_id, title, value, and owner_id

Workflow Canvas > + Add a Step > Run Node.js Code

Add a Node.js code step to resolve stage names and filter

Click the '+ Add a step' button below the trigger and select 'Run Node.js code'. This step does two things: calls the Pipedrive API to resolve stage_id to a human-readable stage name, and filters out deal updates that aren't actually stage changes. Without this, you'll get Slack noise for every field edit on a deal. Paste the code from the Pro Tip section into the code editor.

1. 1Click '+ Add a step' below the trigger block
2. 2Click 'Run Node.js code'
3. 3Clear the default code in the editor
4. 4Paste the pro tip code into the editor
5. 5Replace YOUR_PIPEDRIVE_API_TOKEN with your actual API token or reference it from environment variables

This code step goes between your Pipedrive trigger and your Slack step. It resolves both stage IDs and owner ID to human-readable names via the Pipedrive REST API, checks whether the stage actually changed, and returns a clean object your Slack step can reference directly. Paste it into a 'Run Node.js code' step — no npm installs needed, it uses the built-in fetch available in Pipedream's Node.js runtime.

export default defineComponent({
  async run({ steps, $ }) {
    const event = steps.trigger.event.body;

export default defineComponent({
  async run({ steps, $ }) {
    const event = steps.trigger.event.body;
    const current = event.current;
    const previous = event.previous;
    const apiToken = process.env.PIPEDRIVE_API_TOKEN;
    const baseUrl = 'https://api.pipedrive.com/v1';

    // Early exit: stage didn't actually change
    if (current.stage_id === previous.stage_id) {
      return { shouldNotify: false, reason: 'Stage unchanged' };
    }

    // Resolve current stage name
    let stageName = `Stage ID ${current.stage_id}`;
    let previousStageName = `Stage ID ${previous.stage_id}`;
    let ownerName = `Owner ID ${current.owner_id}`;

    try {
      const [stageRes, prevStageRes, ownerRes] = await Promise.all([
        fetch(`${baseUrl}/stages/${current.stage_id}?api_token=${apiToken}`),
        fetch(`${baseUrl}/stages/${previous.stage_id}?api_token=${apiToken}`),
        fetch(`${baseUrl}/users/${current.owner_id}?api_token=${apiToken}`)
      ]);

      const stageData = await stageRes.json();
      const prevStageData = await prevStageRes.json();
      const ownerData = await ownerRes.json();

      if (stageData.success) stageName = stageData.data.name;
      if (prevStageData.success) previousStageName = prevStageData.data.name;
      if (ownerData.success) ownerName = ownerData.data.name;
    } catch (err) {
      console.error('Pipedrive API lookup failed:', err.message);
      // Continue with fallback IDs rather than crashing the workflow
    }

    const dealValue = current.value
      ? `${Number(current.value).toLocaleString('en-US')} ${current.currency}`
      : 'No value set';

    const dealUrl = `https://app.pipedrive.com/deal/${current.id}`;

    const isWon = stageName.toLowerCase().includes('won');
    const emoji = isWon ? ':trophy:' : ':arrow_right:';

    return {
      shouldNotify: true,
      dealTitle: current.title,
      previousStageName,
      stageName,
      dealValue,
      ownerName,
      dealUrl,
      emoji,
      slackMessage: `${emoji} *${current.title}* moved from *${previousStageName}* → *${stageName}*\n💰 ${dealValue} | 👤 ${ownerName}\n🔗 <${dealUrl}|View in Pipedrive>`
    };
  }
});

Workflow Canvas > + Add a Step > Filter

Add a filter step to halt non-stage-change events

Click '+ Add a step' and select 'Filter'. Set the condition to: the field 'shouldNotify' from the previous code step equals true. If this condition is false, Pipedream stops execution and doesn't send a Slack message. This is what prevents noise from deal title edits, note additions, or other non-stage field updates hitting your Slack channel.

1. 1Click '+ Add a step'
2. 2Click 'Filter' from the step type list
3. 3Click '+ Add condition'
4. 4Set the left side to reference the previous step's 'shouldNotify' output
5. 5Set the operator to 'is true'

Workflow Canvas > + Add a Step > Slack > Send a Message

Add the Slack step to send the notification

Click '+ Add a step', search for 'Slack', and select the 'Send a Message' action. Connect your Slack account using Pipedream's Connected Accounts — this uses OAuth so no bot token copying is required. Set the Channel field to the Slack channel name where you want notifications (e.g., #pipeline-alerts). Build the message text using data from your code step output.

1. 1Click '+ Add a step'
2. 2Search for 'Slack' and click it
3. 3Select 'Send a Message (Advanced)' to get Block Kit support
4. 4Click 'Connect Slack Account' and authorize via OAuth
5. 5Set Channel to your target channel name, e.g. #pipeline-alerts

Workflow Canvas > Slack Step > Blocks Field

Build the Slack message using Block Kit

In the Slack step's 'Blocks' field, enter a JSON Block Kit structure that references your code step outputs. Use the expression syntax (double curly braces or Pipedream's reference picker) to insert deal title, stage name, deal value, and owner name. A well-structured message takes 4 fields from the code step and formats them into a readable Slack card with an emoji header.

1. 1Click into the 'Blocks' field in the Slack step
2. 2Switch to the JSON editor mode
3. 3Paste your Block Kit JSON structure
4. 4Use Pipedream's reference picker to insert dynamic values like {{steps.code.$return_value.dealTitle}}
5. 5Set the 'Text' fallback field to a plain-text summary for notification previews

Workflow Canvas > Three-dot Menu > Add Error Handler

Add error handling with a catch-all email or Slack DM

Click '+ Add a step' and select 'Add Error Handler' from the workflow menu (the three-dot icon on the canvas). Configure it to send a Slack DM to yourself or fire an email if any step throws. Without this, silent failures mean your team misses stage alerts and you have no idea why. Pipedream error handlers run when any upstream step throws an uncaught exception.

1. 1Click the three-dot menu icon on the workflow canvas toolbar
2. 2Click 'Add Error Handler'
3. 3Add a Slack step inside the error handler pointing to a #alerts-internal channel
4. 4Reference {{error.message}} and {{error.step}} in the message body

pipedream.com > Workflow Canvas > Deploy Button

Deploy the workflow and verify live

Click the grey 'Deploy' button in the top right of the canvas. The button turns green and shows 'Active'. Now go into Pipedrive and move a real deal from one stage to another. Watch the Pipedream workflow's event log — you should see the event arrive, both steps execute green, and the Slack message land in your channel within 10 seconds. Check that stage names are human-readable and the deal value shows the correct currency.

1. 1Click the 'Deploy' button in the top right
2. 2Confirm the workflow status shows 'Active' in green
3. 3Open Pipedrive and move a test deal to a new stage
4. 4Check the Pipedream event log under the workflow's 'Logs' tab
5. 5Verify the Slack message appears in your channel with correct data