How to Send Pipedrive Deal Stage Alerts to Slack with n8n

n8n Canvas > + New Workflow

Create a new n8n workflow

Open your n8n instance and click the '+ New Workflow' button in the top-right corner of the canvas. Give it a name like 'Pipedrive → Slack Deal Stage Alerts'. You'll start with an empty canvas and a single 'Start' node placeholder. Delete that placeholder — you'll replace it with a webhook trigger in the next step.

1. 1Click '+ New Workflow' in the top-right corner
2. 2Click the workflow name field at the top and type 'Pipedrive → Slack Deal Stage Alerts'
3. 3Click the default 'Start' node and press Delete to remove it

Canvas > + > Search 'Webhook' > Webhook (Core)

Add a Webhook trigger node

Click the '+' button in the center of the canvas to open the node browser. Search for 'Webhook' and select the core Webhook node. Set the HTTP method to POST. n8n will generate a unique webhook URL — copy this URL immediately, you'll paste it into Pipedrive in the next step. Switch the 'Response Mode' to 'Respond Immediately' so Pipedrive's webhook doesn't time out waiting for a reply.

1. 1Click the '+' button on the canvas
2. 2Type 'Webhook' in the search box and select the 'Webhook' core node
3. 3Set HTTP Method to 'POST'
4. 4Set Response Mode to 'Respond Immediately'
5. 5Copy the Production webhook URL shown in the node panel

Pipedrive > Settings > Tools & Integrations > Webhooks > + Add Webhook

Register the webhook in Pipedrive

Go to your Pipedrive account, open Settings, and navigate to Tools & Integrations > Webhooks. Click '+ Add Webhook'. Paste the n8n Production webhook URL into the Endpoint URL field. Set the Event Action to 'Updated' and the Event Object to 'Deal'. Leave authentication blank unless your n8n instance is public-facing, in which case add HTTP Basic Auth credentials here and mirror them in your n8n Webhook node.

1. 1In Pipedrive, click your avatar and select 'Settings'
2. 2Navigate to 'Tools & Integrations' then click 'Webhooks'
3. 3Click '+ Add Webhook'
4. 4Paste your n8n Production webhook URL into 'Endpoint URL'
5. 5Set Event Action to 'Updated' and Event Object to 'Deal'
6. 6Click 'Save'

n8n Canvas > Webhook Node > Listen for Test Event

Test the webhook with a real deal move

In n8n, click 'Listen for Test Event' on the Webhook node. In Pipedrive, open any deal and drag it to a different stage. Return to n8n — you should see the raw JSON payload appear in the Webhook node's output panel on the right. Expand the 'current' and 'previous' objects inside 'meta' to confirm you can see stage_id in both. This live payload becomes your field map for the next steps.

1. 1Click the Webhook node to open its panel
2. 2Click 'Listen for Test Event' at the bottom of the panel
3. 3Switch to Pipedrive and drag a deal to a new stage
4. 4Return to n8n and confirm the payload appears in the Output tab

Canvas > + > Search 'IF' > IF (Core)

Add an IF node to filter stage changes only

Add an IF node connected to the Webhook node. You need to confirm the deal's stage_id actually changed — Pipedrive fires the webhook for all deal edits, not just stage moves. In the payload, the relevant path is 'body.previous.stage_id' and 'body.current.stage_id'. Set the IF condition to check that these two values are NOT equal. Deals that did not change stage exit through the 'false' branch and stop there.

1. 1Click the '+' connector from the Webhook node
2. 2Search for 'IF' and select the 'IF' core node
3. 3Click 'Add Condition' and set the left value to expression: {{ $json.body.previous.stage_id }}
4. 4Set the operator to 'Not Equal'
5. 5Set the right value to expression: {{ $json.body.current.stage_id }}

Canvas > IF Node (true branch) > + > Search 'Code' > Code (Core)

Add a Code node to resolve stage name and build the message

The Pipedrive webhook gives you stage_id (a number) not the stage name. Add a Code node on the 'true' branch of the IF node. Use a JavaScript object that maps your stage IDs to readable names — you'll find your stage IDs in Pipedrive under Settings > Pipeline. The Code node also builds the Slack message text and decides which Slack channel to target based on stage. This avoids hardcoding channel names in the Slack node and keeps all routing logic in one place.

1. 1Click the '+' on the 'true' output of the IF node
2. 2Search for 'Code' and select the 'Code' core node
3. 3Set Language to 'JavaScript'
4. 4Paste the stage-mapping and message-building code into the code editor (see Pro Tip below)
5. 5Click 'Execute Node' to test with the captured payload

Paste this into the Code node (Step 6). It maps stage IDs to names and Slack channels, formats the message with emoji and currency, and routes Closed Won deals to a separate celebration channel. Update the stageMap object with your own Pipedrive stage IDs — the structure stays the same.

// n8n Code Node — Pipedrive Deal Stage Notification Builder
// Replace stage IDs in stageMap with your actual Pipedrive stage IDs
// Find them at: Pipedrive > Settings > Pipelines

// n8n Code Node — Pipedrive Deal Stage Notification Builder
// Replace stage IDs in stageMap with your actual Pipedrive stage IDs
// Find them at: Pipedrive > Settings > Pipelines

const item = $input.first().json;

const currentStageId = String(item.body?.current?.stage_id);
const dealTitle = item.body?.current?.title ?? 'Unknown Deal';
const dealValue = item.body?.current?.value ?? 0;
const currency = item.body?.current?.currency ?? 'USD';
const ownerName = item.body?.current?.owner_name ?? 'Unassigned';
const orgName = item.body?.current?.org_name ?? 'No Company';
const dealId = item.body?.current?.id;
const dealUrl = `https://app.pipedrive.com/deals/${dealId}`;

// Map your Pipedrive stage IDs to readable names and target Slack channels
const stageMap = {
  '10': { name: 'Qualified',      channel: '#pipeline-updates', emoji: '🔍' },
  '11': { name: 'Demo Scheduled', channel: '#pipeline-updates', emoji: '📅' },
  '12': { name: 'Demo Done',      channel: '#pipeline-updates', emoji: '✅' },
  '13': { name: 'Proposal Sent',  channel: '#pipeline-updates', emoji: '📄' },
  '14': { name: 'Negotiation',    channel: '#pipeline-updates', emoji: '🤝' },
  '15': { name: 'Closed Won',     channel: '#deals-won',        emoji: '🎉' },
  '16': { name: 'Closed Lost',    channel: '#deals-lost',       emoji: '❌' },
};

const stage = stageMap[currentStageId];

if (!stage) {
  throw new Error(`Unknown stage ID: ${currentStageId}. Add it to stageMap in the Code node.`);
}

// Format currency value
const formattedValue = new Intl.NumberFormat('en-US', {
  style: 'currency',
  currency: currency,
  maximumFractionDigits: 0,
}).format(dealValue);

// Build the Slack message text
let messageText;
if (currentStageId === '15') {
  messageText = [
    `🎉 *DEAL CLOSED WON: ${dealTitle}*`,
    `👤 Owner: ${ownerName} | 🏢 ${orgName} | 💰 ${formattedValue}`,
    `🔗 ${dealUrl}`,
  ].join('\n');
} else {
  messageText = [
    `${stage.emoji} *Deal Advanced:* ${dealTitle} moved to *${stage.name}*`,
    `👤 Owner: ${ownerName} | 🏢 ${orgName} | 💰 ${formattedValue}`,
    `🔗 ${dealUrl}`,
  ].join('\n');
}

return [{
  json: {
    channel: stage.channel,
    message_text: messageText,
    stage_name: stage.name,
    deal_title: dealTitle,
    deal_value: dealValue,
    owner_name: ownerName,
    deal_url: dealUrl,
  }
}];

Canvas > Code Node > + > Search 'Slack' > Slack > Message > Post

Connect a Slack node to post the notification

Add a Slack node connected to the Code node. Set Resource to 'Message' and Operation to 'Post'. For the Channel field, use the expression '{{ $json.channel }}' so the Code node controls routing. For the Text field, use '{{ $json.message_text }}'. Connect your Slack credential — you'll need a Slack Bot Token with chat:write scope. The bot must be invited to every channel you plan to post in.

1. 1Click '+' from the Code node and search for 'Slack'
2. 2Select Resource: 'Message', Operation: 'Post'
3. 3In the Channel field, click the expression toggle and type: {{ $json.channel }}
4. 4In the Text field, click the expression toggle and type: {{ $json.message_text }}
5. 5Click 'Create new credential' and paste your Slack Bot Token (starts with xoxb-)
6. 6Click 'Save' on the credential

Canvas > Slack Node > ⋮ Menu > Settings > Continue on Error

Add error handling with a separate Slack alert

Add an Error Trigger node as a second, separate workflow or connect an 'On Error' path from the Slack node to a second Slack message node that posts to a private #n8n-errors channel. This catches Slack API failures and Pipedrive payload parsing errors before they silently drop deals. In n8n, click the three-dot menu on any node and select 'Settings' to configure error output behavior.

1. 1Click the three-dot menu (⋮) on the Slack node
2. 2Select 'Settings'
3. 3Toggle 'Continue on Error' to ON
4. 4Add a second Slack node connected to the error output
5. 5Set its channel to a private ops channel like #workflow-errors
6. 6Set the message text to: 'Deal stage alert failed. Deal ID: {{ $json.body.current.id }}. Error: {{ $json.error.message }}'

n8n Canvas > Top-right toggle > Activate

Activate the workflow

Click the 'Inactive' toggle in the top-right corner of the n8n canvas to set the workflow to 'Active'. This switches from the test webhook URL to the production webhook URL and enables continuous execution. Confirm activation by moving a deal in Pipedrive and checking the target Slack channel within 10-15 seconds. Also check the n8n Executions log to confirm the run shows as 'Success'.

1. 1Click the 'Inactive' toggle in the top-right of the canvas
2. 2Confirm the modal prompt by clicking 'Activate Workflow'
3. 3Open Pipedrive and move a deal to a new stage
4. 4Check the target Slack channel for the notification
5. 5Open n8n > Executions to verify the run shows green 'Success'