How to Connect n8n to Pipedrive: The Complete Integration Guide (2025)

If you run sales on Pipedrive, you already know the CRM is only as good as the data flowing into it — and how fast your team reacts to it. That's exactly where n8n comes in. In this guide you'll learn how to connect n8n to Pipedrive end to end: what the Pipedrive node does, how to generate API credentials, which triggers and actions you'll actually use, and a working step-by-step workflow that turns a new website lead into a Pipedrive deal plus a Slack alert. No fluff — just the moving parts and the gotchas.

What the Pipedrive node in n8n actually does

n8n ships with a native Pipedrive integration split into two building blocks:

• Pipedrive Trigger — a webhook-based node that fires your workflow the moment something changes in Pipedrive (a deal is created, a stage moves, an activity is added). n8n registers the webhook with Pipedrive for you, so you don't manually configure anything inside the CRM.
• Pipedrive (action) node — the regular node you drop into the middle or end of a workflow to read or write data: create a deal, update a person, add a note, log an activity, search organizations, and so on.

Under the hood both talk to the Pipedrive REST API, but n8n abstracts the endpoints into resource/operation dropdowns (Resource: Deal → Operation: Create). You pick fields from a form instead of hand-building JSON payloads.

Step 1: Get your Pipedrive API credentials

Pipedrive supports two auth methods in n8n. For a single-account internal automation, the API token is the fastest path:

1. Log into Pipedrive and click your avatar (top right) → Personal preferences.
2. Open the API tab. You'll see your personal API token — copy it.
3. Note your company domain too. It's the subdomain in your Pipedrive URL, e.g. yourcompany in yourcompany.pipedrive.com. Some operations and the webhook registration rely on it.

If you're building something that other users will authorize (an agency scenario, or a public app), use OAuth2 instead — it avoids sharing personal tokens and respects each user's permissions. For most in-house builds, the token is fine.

Adding the credential in n8n

1. In your n8n canvas, add a Pipedrive node.
2. In the Credential to connect with dropdown, choose Create New.
3. Select Pipedrive API Token, paste the token, and save.
4. Hit Test — n8n makes a lightweight call to confirm the token is valid before you build anything on top of it.

One credential is reused across every Pipedrive node in every workflow, so you only do this once per account.

Common triggers: reacting to Pipedrive events

The Pipedrive Trigger node lets you subscribe to events by object and action. The ones you'll reach for most:

• New deal (object: deal, action: added) — kick off onboarding, notify a rep, log the deal to a sheet.
• Deal updated (object: deal, action: updated) — the workhorse for stage-change automations. The payload includes both current and previous objects, so you can detect exactly what changed (e.g. stage_id moved from 3 to 4) with an IF node.
• Activity added / updated — trigger follow-up logic when a call or meeting is logged.
• Person or organization added — sync new contacts to a marketing tool or enrich them.

A practical tip on deal updated: Pipedrive fires it on any field change, so it's noisy. Always follow the trigger with a filter that compares previous.stage_id to current.stage_id (or whichever field you care about) so downstream steps only run when the change is meaningful.

Common actions: writing back to Pipedrive

On the action side, the operations you'll use constantly:

• Create Deal — needs a title at minimum; optionally value, currency, stage_id, person_id, and org_id.
• Update Deal — move a stage, change status to won/lost, adjust value.
• Create Person — name is required; add email and phone as arrays. Link them to an org with org_id.
• Add Activity — schedule a call or task tied to a deal via deal_id, with subject, type, and due_date.
• Search / Get — look up a person by email before creating a duplicate. This dedup check is the single most valuable habit when syncing leads in.

Step-by-step: new website lead → Pipedrive deal → Slack alert

Here's a concrete workflow you can build in about ten minutes. Goal: a form submission on your site creates a deal in Pipedrive and pings your sales channel in Slack.

1. Trigger — Webhook node. Add a Webhook node, set method to POST, and copy its URL into your website form's endpoint (or your form tool like Typeform/Elementor). Incoming fields: name, email, company, message.
2. Dedup — Pipedrive node, Resource: Person, Operation: Search. Search by the submitted email. If a person exists, reuse their person_id; if not, continue to create one.
3. Create Person (only when search returns nothing). Map name and email from the webhook. Capture the returned id.
4. Create Deal — Pipedrive node, Resource: Deal, Operation: Create. Set title to something like {{$json["company"]}} — Website Lead, attach the person_id from the previous step, and set stage_id to your "Inbound" stage.
5. Slack node, Operation: Send Message. Post to #sales: "🔥 New lead: {{$json["name"]}} from {{$json["company"]}} — deal created in Pipedrive." Include the deal URL so a rep can click straight through.

Activate the workflow, submit a test lead, and confirm the deal appears in Pipedrive and the message lands in Slack. That's a full lead-capture pipeline with zero manual data entry.

Skip the build: If you'd rather not wire up the Pipedrive → Slack logic (plus a Google Sheets log for reporting) from scratch, we've packaged the exact workflow — dedup, deal creation, formatted Slack alert, and a running spreadsheet log — ready to import. Get the Pipedrive New Deal → Slack Alert + Google Sheets Log template on Gumroad →

Pagination and rate limits: the part people skip

When you're reading lists from Pipedrive (all open deals, all people), a single API call won't return everything. Two things to handle:

• Pagination. Pipedrive uses start and limit parameters and returns an additional_data.pagination block with more_items_in_collection and next_start. In n8n, the Get Many operations expose a Return All toggle — turn it on and n8n loops through pages for you. If you're using the HTTP Request node instead, enable its pagination options and reference next_start as the offset.
• Rate limits. Pipedrive enforces a per-token budget (a token-bucket system, roughly a few hundred requests per short window depending on your plan). If you fire a big batch — say, updating 2,000 deals — add a Loop Over Items (batch) node with a small Wait node between batches, or set the node's retry-on-fail so a 429 response backs off instead of killing the run.

For scheduled bulk syncs, run them off-peak and page in chunks of 100–500. You'll stay well under the ceiling and avoid throttling mid-job.

Three practical use cases

• Lead routing with enrichment. On new deal, call an enrichment API (Clearbit, Apollo) to fill in company size and industry, then update the deal's custom fields and assign an owner based on territory — all before the rep even opens it.
• Won-deal handoff. On deal updated, filter for status = won, then create an onboarding project in Asana/ClickUp, generate an invoice in Stripe, and post a 🎉 message to #wins. The whole post-sale kickoff runs itself.
• Stale-deal nudges. On a schedule, pull all open deals with Return All, filter for those untouched in 14+ days, and add a Pipedrive activity ("Follow up — deal gone cold") assigned to the deal owner so nothing rots in the pipeline.

Wrapping up

Connecting n8n to Pipedrive comes down to three things: a valid API credential, the right trigger for the event you care about, and action nodes that write clean, de-duplicated data back. Once that foundation is in place, everything from lead capture to won-deal handoffs becomes a workflow instead of a manual chore. Start with the lead-to-deal-to-Slack pipeline above, then layer on enrichment and follow-up automations as your team's needs grow.

Ready to automate? Get this template on Gumroad →