See llms.txt for all machine-readable content.

Pipedrive and Salesforce integration

Save yourself the work of writing custom integrations for Pipedrive and Salesforce and use n8n instead. Build adaptable and scalable Sales, workflows that work with your technology stack. All within a building experience you will love.

How to connect Pipedrive and Salesforce

Create a new workflow and add the first step

In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.

Pipedrive and Salesforce integration: Create a new workflow and add the first step

Automate B2B SaaS renewal risk management with CRM, support & usage data

Description This workflow is designed for B2B/SaaS teams who want to secure renewals before it’s too late. It runs every day, identifies all accounts whose licenses are up for renewal in J–30, enriches them with CRM, product usage and support data, computes an internal churn risk level, and then triggers the appropriate playbook: HIGH risk → full escalation (tasks, alerts, emails) MEDIUM risk → proactive follow-up by Customer Success LOW risk → light renewal touchpoint / monitoring Everything is logged into a database table so that you can build dashboards, run analysis, or plug additional automations on top. How it works image.png Daily detection (J–30 renewals) A scheduled trigger runs every morning and queries your database (Postgres / Supabase) to fetch all active subscriptions expiring in 30 days. Each row includes the account identifier, name, renewal date and basic commercial data. Data enrichment across tools For each account, the workflow calls several business systems to collect context: HubSpot → engagement history Salesforce → account profile and segment Pipedrive → deal activities and associated products Analytics API → product feature usage and activity trends Zendesk → recent support tickets and potential friction signals All of this is merged into a single, unified item. Churn scoring & routing An internal scoring step evaluates the risk for each account based on multiple signals (engagement, usage, support, timing). The workflow then categorizes each account into one of three risk levels: HIGH – strong churn signals → needs immediate attention MEDIUM – some warning signs → needs proactive follow-up LOW – looks healthy → light renewal reminder A Switch node routes each account to the relevant playbook. Automated playbooks 🔴 HIGH risk Create a Trello card on a dedicated “High-Risk Renewals” board/list Create a Jira ticket for the CS / AM team Send a Slack alert in a designated channel Send a detailed email to the CSM and/or account manager 🟠 MEDIUM risk Create a Trello card in a “Renewals – Follow-up” list Send a contextual email to the CSM to recommend a proactive check-in 🟢 LOW risk Send a soft renewal email / internal note to keep the account on the radar Logging & daily reporting For every processed account, the workflow prepares a structured log record (account, renewal date, risk level, basic context). A Postgres node is used to insert the data into a churn_logs table. At the end of each run, all processed accounts are aggregated and a daily summary email is sent (for example to the Customer Success leadership team), listing the renewals and their risk levels. Requirements Database A table named churn_logs (or equivalent) to store workflow decisions and history. Example fields: account_id, account_name, end_date, riskScore, riskLevel, playbook, trello_link, jira_link, timestamp. External APIs HubSpot (engagement data) Salesforce (account profile) Pipedrive (deals & products) Zendesk (support tickets) Optional: product analytics API for usage metrics Communication & task tools Gmail (emails to CSM / AM / summary recipients) Slack (alert channel for high-risk cases) Trello (task creation for CS follow-up) Jira (escalation tickets for high-risk renewals) Configuration variables Thresholds are configured in the Init config & thresholds node: days_before_renewal churn_threshold_high churn_threshold_medium These parameters let you adapt the detection window and risk sensitivity to your own business rules. Typical use cases Customer Success teams who want a daily churn watchlist without exporting spreadsheets. RevOps teams looking to standardize renewal playbooks across tools. SaaS companies who need to prioritize renewals based on real risk signals rather than gut feeling. Product-led organizations that want to combine usage data + CRM + support into one automated process. Tutorial video Watch the Youtube Tutorial video About me : I’m Yassin a Project & Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin

Popular ways to use the Pipedrive and Salesforce integration

Build your own Pipedrive and Salesforce integration

Create custom Pipedrive and Salesforce workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.

Pipedrive supported actions

Salesforce supported actions

Pipedrive and Salesforce integration details

Pipedrive

Pipedrive

Pipedrive is a sales-focused Customer Relationship Management tool that teams of all sizes love using. At the core of Pipedrive is pipeline management, and it features key sales functionalities: automations, email integration and a decent selection of partner integrations.

Salesforce

Salesforce

Salesforce is one of the best cloud-based CRM (Customer Relationship Management) platform. It is an integrated CRM that provides a single shared view of each customer for all the departments within an organization, such as Marketing, Sales, Commerce, and Service.

Supercharge your CRM

Need a more powerful integration with your CRM? n8n lets you go beyond standard integrations offered by popular CRMs!

Learn more

FAQ about Pipedrive integrations

Need help setting up your Pipedrive and Salesforce integration?

Discover our latest community's recommendations and join the discussions about Pipedrive and Salesforce integration.

  • trijste

    Help getting the MCP trigger to pass a variable into an http request tool

    trijste

    I’m trying to build an MCP server that has access to my Salesforce org, but only at the schema and describe object level, ideally to provide more information for building out SOQL queries using custom fields from custom …

    Open topic
  • DV

    Salesforce platform events capture - to trigger N8n flow

    DV

    I could not find node of trigger type, which will start workflow when “platform event is publishjed from salesforce”. I am looking for support in n8n to listen to platform event as soon as published by SalesForce.

    Open topic
  • Graeme Smith

    How to connect credentials to Salesforce Custom Domain?

    Graeme Smith

    Describe the problem/error/question Unable to create credentials (oauth) for salesforce sandbox with custom domain What is the error message (if any)? error=redirect_uri_mismatch redirect_url_must_match_configuration I…

    Open topic

Looking to integrate Slack and VirusTotal in your company?

Trusted by teams building smarter workflows

Why

Why use n8n to integrate Pipedrive with Salesforce

Handle branching, merging and iteration easily. Pause your workflow to wait for external events.

Re-run single steps to test changes in no time. And pin your data to avoid generating trigger events every time you execute.

Your data is displayed alongside your settings, making edge cases easy to track down.

Use 1000+ workflow templates available from our core team and our community.

Copy and paste, easily import and export workflows.

Simple enough to 
understand + sophisticated 
enough to ship