Most-used Pipedrive workflows
- Sync Contacts, Consent, and Segments Between Klicktipp and Pipedrive (36 nodes)
- Generate & Send Quotation Pdfs From Pipedrive to Dottedsign for E-signature — n8n Pipedrive workflow (35 nodes)
- Automate B2b SAAS Renewal Risk Management with Crm, Support & Usage Data (33 nodes)
- Vet New Form.io Leads with Zerobounce and Sync Qualified Contacts to Pipedrive — n8n Pipedrive workflow (30 nodes)
- Sync Webflow Form Leads to Pipedrive with Discord and Gmail Notifications (27 nodes)
- Functionitem Zendesk — n8n Pipedrive workflow (21 nodes)
- Sync Zendesk Tickets to Pipedrive Contact Owners (21 nodes)
- Splitout Filter (clearbit) — n8n Pipedrive workflow (20 nodes)
- Enrich New Leads in Pipedrive and Send an Alert to Slack for High-quality Ones (20 nodes)
- Sync CRM Contacts with Mailchimp and Pipedrive — n8n Pipedrive workflow (19 nodes)
This workflow uses KlickTipp community nodes, available for self-hosted n8n instances only.
Description:
This workflow is designed for B2B/SaaS teams who want to secure renewals before it’s too late.
This workflow automates the transition of new Form.io submissions into Pipedrive, using ZeroBounce for multi-layer validation (Validation + AI Scoring).
This workflow is for sales and marketing teams using Webflow as their primary lead capture tool and Pipedrive as their CRM. It automates the entire lead intake process, from form submission to CRM ent
Functionitem Zendesk. Uses noOp, functionItem, httpRequest, zendesk. Scheduled trigger; 21 nodes.
This workflow syncs Zendesk tickets to Pipedrive contact owners.
Splitout Filter. Uses stickyNote, clearbit, pipedrive, scheduleTrigger. Scheduled trigger; 20 nodes.
This workflow is beneficial when you're automatically adding new leads to your Pipedrive CRM. Usually, you'd have to manually review each lead to determine if they're a good fit. This process is time-
This workflow keeps your contact records perfectly aligned between your CRM (e.g. HubSpot / Salesforce / Pipedrive) and Mailchimp. Whenever a contact is created or updated in one system, the automatio
CRM Automation, Revenue Operations, Sales Operations, Meeting Automation
This workflow is designed for sales teams and business development managers who use Pipedrive to track leads and Google Calendar to schedule discovery calls. It automates the sending of commercial bri
Functionitem Zendesk. Uses functionItem, zendesk, pipedrive, httpRequest. Scheduled trigger; 17 nodes.
This workflow automatically sends Zendesk tickets to Pipedrive contacts and makes them task assignees. The automation is triggered every 5 minutes, with Zendesk checking and collecting new tickets whi
Problem: Your ads and GA4 often optimize to shallow web events (form fills), while the real value sits in Pipedrive (Qualified, Closed Won). That gap means bidding chases cheap leads instead of revenu
n8n instance (cloud or self-hosted) with HTTPS reachable webhook endpoint Stripe account and secret API key Pipedrive account with API access and custom fields defined Users should create custom field
⚠️ COMMUNITY TEMPLATE DISCLAIMER: This is a community-contributed template that uses ScrapeGraphAI (a community node). Please ensure you have the ScrapeGraphAI community node installed in your n8n ins
⚠️ COMMUNITY TEMPLATE DISCLAIMER: This is a community-contributed template that uses ScrapeGraphAI (a community node). Please ensure you have the ScrapeGraphAI community node installed in your n8n ins
Hunter Pipedrive. Uses stickyNote, formTrigger, noOp, hunter. Event-driven trigger; 15 nodes.
When collecting leads via an online form, you often need to manually add those new leads into your Pipedrive CRM. This not only takes a lot of time but is also error-prone. This workflow automates thi
This n8n template automates the process of capturing leads from Webflow form submissions and syncing them with your Pipedrive CRM. It ensures that each submission is accurately associated with the cor
Two Way Sync Pipedrive and MySQL. Uses compareDatasets, scheduleTrigger, mySql, pipedrive. Scheduled trigger; 14 nodes.
This workflow automates a two way sync of customer data between Pipedrive and MySQL. It will create new records in one source if it only exists in the other. Where matching records have different data
This workflow fetches deals and their notes from Pipedrive, cleans up stage IDs into names, aggregates the information, and uses OpenAI to generate a daily summary of your funnel. Go to OpenAI Platfor
This workflow captures new subscribers from a Mailchimp list and extracts their key details. It then enriches the subscriber data using AI, predicting professional attributes and assigning a lead scor
Pipedrive Spreadsheetfile. Uses googleDriveTrigger, googleDrive, spreadsheetFile, pipedrive. Event-driven trigger; 12 nodes.
This workflow gets leads' contacts from a CSV file and adds it to the Pipedrive CRM by creating an organization and a person. The CSV file in this workflow serves as a universal connector allowing you
Pipedrive Stickynote. Uses itemLists, pipedrive, httpRequest, pipedriveTrigger. Event-driven trigger; 11 nodes.
Code Pipedrive. Uses pipedrive, openAi, gmailTrigger, stickyNote. Event-driven trigger; 11 nodes.
Code Pipedrive. Uses pipedrive, openAi, gmailTrigger, stickyNote. Event-driven trigger; 11 nodes.
Functionitem Pipedrive. Uses stripe, pipedrive, functionItem, itemLists. Scheduled trigger; 11 nodes.
Sync Local Falcon rankings to Pipedrive deals. Uses @local-falcon/n8n-nodes-localfalcon, pipedrive. Scheduled trigger; 11 nodes.
The workflow reads every reply that is received from a cold email campaign and qualifies if the lead is interested in a meeting. If the lead is interested, a deal is made in pipedrive. You can add as
This workflow combines customers' details with their payment data and passes the input to Pipedrive as a note to the organization. Stripe account and Stripe credentials Pipedrive account and Pipedrive
This workflow enriches new accounts in Pipedrive using Datagma API by adding data about ICP (ideal customer profile). Instead of Pipedrive, you can use any other CRM. In this example, ideal buyers are
This workflow pulls deals from Pipedrive, categorizes them by stage, and logs them into a Google Sheet for reporting and tracking. In Pipedrive → Personal preferences → API → copy your API token URL s
Capture Contact Requests: This template efficiently handles contact requests coming through a WordPress website using the Contact Form 7 (CF7) plugin with a webhook extension. Contact Management: It a
piepdrive-test. Uses pipedriveTrigger, stickyNote, pipedrive, httpRequest. Event-driven trigger; 8 nodes.
piepdrive-test. Uses pipedriveTrigger, stickyNote, pipedrive, httpRequest. Event-driven trigger; 8 nodes.
Code Typeform. Uses stickyNote, pipedrive, typeformTrigger. Event-driven trigger; 8 nodes.
Http Github. Uses pipedrive, githubTrigger, httpRequest. Event-driven trigger; 8 nodes.
This workflow enriches new Pipedrive organization's data by adding a note to the organization object in Pipedrive. It assumes there is a custom "website" field in your Pipedrive setup, as data will be
This automated workflow takes a Typeform form, and once it is filled out, it is automatically uploaded as a Lead in Pipedrive. There is an option for custom fields (this workflow works with company si
This workflow automatically adds a new lead to Pipedrive once someone forks your GitHub repository. Pipedrive account and Pipedrive credentials GitHub account and GitHub credentials GitHub Trigger nod
Bring your Eventbrite attendee data into Pipedrive automatically—no spreadsheets, CSVs, or manual uploads. Polls Eventbrite on a schedule (default 30 min) for new registrations. Creates or updates mat
Http Stripe. Uses pipedriveTrigger, pipedrive, httpRequest, stripe. Event-driven trigger; 7 nodes.
This workflow automatically adds closed deals from Pipedrive as new customers into Stripe. Pipedrive account and Pipedrive credentials Stripe account and Stripe credentials Pipedrive trigger node star
Http Github. Uses httpRequest, pipedrive, noOp, githubTrigger. Event-driven trigger; 6 nodes.
This workflow automatically adds a note of the PR from GitHub to the Pipedrive contact if their GitHub email matches a Person in Pipedrive. Pipedrive account and Pipedrive credentials GitHub account a
Hubspot Cron. Uses pipedrive, hubspot. Scheduled trigger; 7 nodes.
This workflow synchronizes data both ways between Pipedrive and HubSpot. Cron node schedules the workflow to run every minute. Pipedrive and Hubspot nodes pull in both lists of persons from Pipedrive
Wait Datetime. Uses calendlyTrigger, pipedrive, dateTime, slack. Event-driven trigger; 5 nodes.
This workflow synchronizes data one-way from Pipedrive to HubSpot. Cron node schedules the workflow to run every minute. Pipedrive and Hubspot1 nodes pull in both lists of persons from Pipedrive and c
Create an deal in Pipedrive. Uses manualTrigger, pipedrive. Event-driven trigger; 2 nodes.
55 of 55 workflows in this view · Browse all →
FAQ
How many n8n Pipedrive workflows are in the catalog?
55 n8n workflows in AutomationFlows currently use the Pipedrive integration — triggers, actions, or both.
How do I connect Pipedrive in n8n?
After importing the workflow JSON, n8n will prompt for Pipedrive credentials on the relevant nodes. AutomationFlows strips credential IDs before publishing — you'll add your own.
Can I combine these with other integrations?
Yes — most Pipedrive workflows pair with adjacent tools (Slack alerts, Google Sheets logging, OpenAI summarisation). Browse the integration tags on each workflow page to discover pairings.