Which events can the Pipedrive Trigger listen to?

An Action (Added, Updated, Deleted, Merged or All) on an Object such as Deal, Person, Organization, Lead, Activity, Note, Product, Pipeline, Stage or User. It registers a Pipedrive webhook.

Pipedrive in n8n: API token or OAuth2?

Both are supported. The API token is quickest for your own company; OAuth2 needs a Pipedrive developer sandbox and an app with the right scopes, and gets four times the burst limit.

Do Pipedrive steps convert automatically?

Not yet. Each Pipedrive action arrives as a placeholder with its props, and the report lists the Pipedrive credential to create.

Why does search fail in loops?

Pipedrive caps search at 10 requests per 2 seconds on every plan and charges 40 tokens per search against the daily budget. Search once and cache, or add a Wait node.

Pipedream Pipedrive steps in n8n

Updated 2026-10-21 · 3 min read · n8n: Pipedrive (Native n8n node)

Pipedrive workflows on Pipedream feed the pipeline: a form submission becomes a person and a deal, a won deal triggers an invoice or a Slack message. n8n has a native Pipedrive node and a webhook Pipedrive Trigger, so the structure carries over almost one to one.

The n8n side

Pipedrive node (n8n-nodes-base.pipedrive) resources: Activity, Deal, Deal Product, File, Lead, Note, Organization, Person, Product (plus Deal Activity in node version 1). Deals, persons, organizations, leads, notes and activities all have Create, Delete, Get, Get Many and Update; Deal also has Duplicate and Search, Person and Organization have Search. The node is versioned and new nodes use version 2, which adds full product operations.

Pipedrive Trigger: a webhook with two settings, Action (Added, Updated, Deleted, Merged, All) and Object (Deal, Person, Organization, Lead, Activity, Note, Product, Pipeline, Stage, User, Activity Type, All). Incoming requests can be protected with Basic Auth.

What maps where

Pipedream (app `pipedrive`)	In n8n	Status
Add Deal / Update Deal	Deal → Create / Update	manual
Add Person, Add Organization	Person → Create, Organization → Create	manual
Add Lead	Lead → Create	manual
Add Activity, Add Note	Activity → Create, Note → Create	manual
Search persons	Person → Search	manual
New Deal (Instant), Deal Updated (Instant)	Pipedrive Trigger, Object Deal, Action Added / Updated	manual
New Person (Instant), Person Updated (Instant)	Pipedrive Trigger, Object Person	manual
Lead Updated (Instant)	Pipedrive Trigger, Object Lead, Action Updated	manual
New Event (Instant)	Pipedrive Trigger, Object All, Action All	manual

The converter does not map Pipedrive actions yet: each step becomes a placeholder with its props in a comment, the trigger a Manual Trigger naming the source, and the report lists the Pipedrive credential.

Pipedrive credentials in n8n

API token: Personal preferences → API in Pipedrive. Simple and fine for one company.
OAuth2: create an app in a developer sandbox, choose scopes; the n8n docs list which scope each node operation needs.

Typical migration: won deal to invoice

Pipedream: Pipedrive Deal Updated (Instant) → filter status = won → QuickBooks create invoice. n8n: Pipedrive Trigger (Deal, Updated) → If (deal status is won and the previous status in the webhook payload is not) → QuickBooks → Invoice → Create. Checking the previous value avoids a second invoice when someone edits a won deal. Run one test event first: the payload shape depends on the trigger version (webhooks v1 vs v2).

Pipedrive migration pitfalls

Token budget. Pipedrive gives each company a daily budget of 30,000 tokens × plan multiplier × seats; a GET costs 2 tokens, a search 40. Over budget you get 429 until midnight.
Burst limit. API tokens get 20 requests per 2 seconds on Lite up to 120 on Ultimate; OAuth apps get four times that. Clients that ignore 429 can be blocked with a Cloudflare 403.
Custom fields are 40-character hash keys. Copy them from the Pipedream props; the n8n node shows them in Additional Fields → Custom Properties.
Duplicate webhooks. Delete Pipedream's webhooks in Pipedrive → Tools → Webhooks after the switch.

How to move your Pipedrive workflows

Export the workflows from Pipedream.
Upload on /convert; the free report shows each Pipedrive step and its props.
Get the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

See the Pipedream to n8n guide. Related: HubSpot, Zoho CRM, Salesforce.

FAQ

Which events can the Pipedrive Trigger listen to?: An Action (Added, Updated, Deleted, Merged or All) on an Object such as Deal, Person, Organization, Lead, Activity, Note, Product, Pipeline, Stage or User. It registers a Pipedrive webhook.
Pipedrive in n8n: API token or OAuth2?: Both are supported. The API token is quickest for your own company; OAuth2 needs a Pipedrive developer sandbox and an app with the right scopes, and gets four times the burst limit.
Do Pipedrive steps convert automatically?: Not yet. Each Pipedrive action arrives as a placeholder with its props, and the report lists the Pipedrive credential to create.
Why does search fail in loops?: Pipedrive caps search at 10 requests per 2 seconds on every plan and charges 40 tokens per search against the daily budget. Search once and cache, or add a Wait node.