Most-used Pipedrive Trigger workflows
- Enrich CRM Contact Data with Linkedin Profiles Using Gpt & Multi-crm Support (42 nodes)
- Sync Contacts, Consent, and Segments Between Klicktipp and Pipedrive — n8n Pipedrive Trigger workflow (36 nodes)
- Generate & Send Quotation Pdfs From Pipedrive to Dottedsign for E-signature (35 nodes)
- Schedule and Confirm Revenue Ops Meetings with Pipedrive, Google Calendar and Slack — n8n Pipedrive Trigger workflow (18 nodes)
- Connect Pipedrive Deal Outcomes to Ga4 & Google Ads via Measurement Protocol (17 nodes)
- Pipedrive Stickynote — n8n Pipedrive Trigger workflow (11 nodes)
- Enrich New Accounts in Pipedrive Using Datagma API (11 nodes)
- Piepdrive Test — n8n Pipedrive Trigger workflow (8 nodes)
- Piepdrive Test (pipedrive Trigger) (8 nodes)
- Enrich Pipedrive's Organization Data with Openai Gpt-4o & Notify It in Slack — n8n Pipedrive Trigger workflow (8 nodes)
⚠️ DISCLAIMER: This workflow uses the AnySite LinkedIn community node, which is only available on self-hosted n8n instances. It will not work on n8n.cloud.
This workflow uses KlickTipp community nodes, available for self-hosted n8n instances only.
Description:
CRM Automation, Revenue Operations, Sales Operations, Meeting Automation
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
Pipedrive Stickynote. Uses itemLists, pipedrive, httpRequest, pipedriveTrigger. Event-driven trigger; 11 nodes.
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
piepdrive-test. Uses pipedriveTrigger, stickyNote, pipedrive, httpRequest. Event-driven trigger; 8 nodes.
piepdrive-test. Uses pipedriveTrigger, stickyNote, pipedrive, 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
Http Stripe. Uses pipedriveTrigger, pipedrive, httpRequest, stripe. Event-driven trigger; 7 nodes.
Functionitem Http. Uses pipedriveTrigger, functionItem, httpRequest, itemLists. Event-driven trigger; 7 nodes.
This workflow adds a new product in Stripe whenever a new product has been added to Pipedrive. Stripe account and Stripe credentials Pipedrive account and Pipedrive credentials Pipedrive trigger node
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
14 of 14 workflows in this view · Browse all →
FAQ
How many n8n Pipedrive Trigger workflows are in the catalog?
14 n8n workflows in AutomationFlows currently use the Pipedrive Trigger integration — triggers, actions, or both.
How do I connect Pipedrive Trigger in n8n?
After importing the workflow JSON, n8n will prompt for Pipedrive Trigger 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 Trigger workflows pair with adjacent tools (Slack alerts, Google Sheets logging, OpenAI summarisation). Browse the integration tags on each workflow page to discover pairings.