Connecting Pipedrive to n8n: the complete guide (credentials, node, trigger)

A lead who fills out a form and waits an hour without a reply is seven times less likely to end up in a qualified conversation than one contacted within five minutes: that's the finding of a study by Oldroyd, McElheran, and Elkington published in 2011 in the Harvard Business Review, which analyzed 1.25 million leads across 43 B2B and B2C companies (Oldroyd et al., 2011). Pipedrive is built precisely for sales execution speed — visual pipelines, scheduled follow-ups — but it stays manual until something connects it to the rest of your stack. This guide covers the essentials for wiring it to n8n: authentication, the native node, the trigger, and the new token-based rate limits that took effect in 2026.

Authentication: API Token or OAuth2

n8n offers two Pipedrive credentials, with a real trade-off behind the choice.

The API Token: the fastest to set up

From Pipedrive, go to Personal preferences → API and copy your personal API token. In n8n: Credentials → New → Pipedrive API — paste the token, done. No consent screen, no refresh token to manage.

The downside: this token is tied to one specific Pipedrive user. If that person leaves the company, changes their password, or has their access revoked, every workflow depending on it stops dead — a risk worth documenting unless the account in use is a dedicated service account.

OAuth2: the right choice for a team

The Pipedrive OAuth2 credential requires creating an app in Pipedrive's Marketplace Developer Hub (a private app for internal use), entering the callback URL n8n provides, then copying the Client ID and Client Secret into the n8n credential. Two scope levels exist: Read only and Full access — choose Full access as soon as a workflow needs to create or update objects.

The decisive advantage for a team: the integration is no longer tied to one person's account, and n8n handles token refresh automatically. The cost: a longer initial setup, done only once. Apply the same precautions as for any API credential — minimal scopes, an isolated secret — detailed in our guide on securing API credentials in n8n.

The Pipedrive Trigger's special case

The Pipedrive Trigger node works with either credential, but the OAuth2 app (or the token's underlying user) needs the Webhooks: Full access scope (webhooks:full) to be able to create the webhook subscription on Pipedrive's side. Without that specific scope, trigger creation fails silently when the workflow is activated — the first thing to check on any error is this scope, before chasing any other lead.

The Pipedrive node: resources and operations

The native node covers nearly the whole CRM: Deal, Person, Organization, Activity, Note, File, Product, Lead, plus the sub-resources Deal Product (products attached to a deal) and Deal Activity. Every resource offers Create, Update, Delete, Get, and Get Many; Deal, Person, and Organization also add a Search operation, useful for checking whether a record already exists before creating a duplicate.

Three patterns show up in most workflows:

• Creating a deal in the right pipeline and stage — both are referenced by their internal ID, visible in Settings → Pipelines and stages, not by the label shown on screen.
• Searching for a person by email before creating a contact — the Person resource's Search operation prevents duplicates when the same prospect comes back through a second channel (form, inbound call).
• Adding a note or a scheduled activity on a deal after an automated action, so the sales rep sees exactly what the automation did directly in the Pipedrive interface — the same traceability logic described in our guide on HubSpot/Pipedrive CRM synchronization with n8n.

The Pipedrive Trigger: reacting in real time

Once the webhooks:full scope is in place, the trigger subscribes to Pipedrive events: creation, update, or deletion of a deal, a person, an organization, an activity, or a note. It's a true push (webhook), not polling — latency is measured in seconds, which matters for capturing the responsiveness window highlighted by the study cited above.

A limitation worth knowing: unlike HubSpot, the Pipedrive Trigger has no dedicated event for Leads (the prospect inbox before conversion into a deal). Two common workarounds: trigger on the creation of the deal that follows lead conversion, or periodically poll the /leads endpoint with a Schedule Trigger paired with an HTTP Request node using the Pipedrive credential as a Predefined Credential Type.

2026 rate limits: a token system, not a request count

Pipedrive changed its rate-limiting model in 2026: every call now consumes tokens drawn from a daily budget specific to the account (reset every 24 hours), and the token cost varies by endpoint complexity — a search costs more than a simple lookup by ID. On top of that, a per-user burst cap applies on a rolling 2-second window, to stop an entire budget from being consumed in one go. Beyond either limit, the API responds with a 429.

Three habits on the n8n side:

1. Loop Over Items + Wait to pace batch processing instead of firing every call in a burst — the same mechanism detailed in our article on API rate limits in n8n, with a Wait node between each chunk.
2. Retry On Fail enabled on the Pipedrive node, to absorb residual 429s without failing the whole execution.
3. Monitor the daily budget from the account's API settings before a large import (a spreadsheet migration, an initial sync) — an insufficient budget is fixed by upgrading a plan or adding seats, not by further optimizing the workflow.

Three quick use cases

• Automatic speed-to-lead: the Pipedrive Trigger detects a new deal, an LLM drafts a personalized first message from the deal's fields, and an email or SMS goes out within seconds — see our guide on Twilio SMS for alerts and follow-ups for the SMS channel.
• AI scoring on deal creation: the trigger kicks off analysis of the context (budget, industry, history) by an LLM, which writes a score to a custom field — the same logic as AI qualification of inbound leads.
• Slack notification on a stage change: the trigger on a deal update filters stage_id changes and feeds a Slack channel with the amount, the stage, and a direct link — the team follows the pipeline without keeping Pipedrive open all day.

The native node's limits

The Pipedrive node covers the day-to-day but not the API's most recent endpoints (v2, some advanced Lead filters). In those cases, the HTTP Request node, configured with the Pipedrive credential as a Predefined Credential Type, calls any endpoint without handling authentication by hand — the same fallback described in our guide on automatic lead enrichment.

Summary

Connecting Pipedrive to n8n comes down to three building blocks: an API Token to get started fast solo (with the risk of depending on one user), an OAuth2 app for a team that wants to decouple the integration from an individual account, and a webhooks:full scope not to forget for the trigger. The native node covers deals, persons, organizations, activities, and leads with built-in search; the new token-based rate limits are handled with the same habits as any high-volume API — pacing and retry. The logical next step: putting intelligence into what enters the pipeline instead of sorting it by hand. The AI Inbox Pack provides ready-to-import workflows that sort and prioritize inbound requests before they land in your CRM — exactly what buys a sales rep the time to respond within the first five minutes.