Pipedrive n8n integrationAutomate Pipedrive with n8n.

Logs a call, a meeting or a task on the Pipedrive timeline and hands the new activity, ID included, to the next node.

• Subject: the line a rep reads in the activity list, so write it like a task.
• Type: the activity type as a plain string, call or meeting.
• Additional Fields: Deal ID, Person ID or Organization Name or ID decide what the activity hangs on, Due Date takes a YYYY-MM-DD date and User Name or ID assigns it to another rep.

Erases one activity. It leaves the timeline of the deal, person or organization it was attached to, and n8n returns the ID that was removed so the workflow can log it.

• Activity ID: the numeric ID of the activity, usually {{ $json.id }} carried over from a search or from the trigger.

Reads a single activity and returns its fields as one item: subject, type, due date, owner and the records it is linked to.

• Activity ID: which activity to read.
• Show Raw Field Keys: off, the output uses human-readable names; on, it shows raw Pipedrive field keys and option IDs, which is what you want when a later node matches on a custom field key.

Returns a list of activities rather than one. The Filters collection cuts the list on the Pipedrive side, so less noise reaches the rest of the workflow.

• Return All: on, n8n walks the pages of the Pipedrive API and brings back every matching activity; off, Limit caps how many come back.
• Filters: Start Date and End Date take due dates in YYYY-MM-DD, Done keeps finished or unfinished activities, User Name or ID narrows to one rep and Deal ID to one deal.

Edits an activity that already exists and leaves every field you did not fill untouched.

• Activity ID: the activity to edit.
• Update Fields: Done closes it, Due Date reschedules it, Subject and Type rewrite the header, User Name or ID hands it to another rep, Busy Flag marks the slot as busy and Public Description syncs extra detail to the external calendar.

Opens a deal in the pipeline and returns it with its ID, ready for whatever the workflow does next.

• Title: the deal name shown on the card.
• Associate With: organization or person; the form then asks for Organization ID or Person ID.
• Additional Fields: Value with Currency as a 3-character code such as EUR, Stage Name or ID to place the card (without it the deal lands in the first stage of the default pipeline), Expected Close Date in YYYY-MM-DD and Visible To.

Deletes a deal from Pipedrive. Nothing brings it back afterwards, so this operation belongs behind a condition rather than straight after a trigger.

• Deal ID: the numeric ID of the deal to delete, taken from a search or from a previous Pipedrive node.

Copies an existing deal into a new one and returns the copy with its own ID. The duplicate arrives as a fresh card, so an update right after it is what sets the dates, the value and the stage of the new cycle.

• Deal ID: the deal used as the model.

Fetches one deal in full: value, currency, stage, owner and the person or organization behind it.

• Deal ID: the deal to read.
• Show Raw Field Keys: switches the output from human-readable names to raw Pipedrive field keys and option IDs.

Lists deals, filtered or not. Everything the Filters collection does happens on the Pipedrive side, which keeps the payload small.

• Return All: on, every page of results comes back; off, Limit decides how many deals the node returns.
• Filters: Status defaults to all_not_deleted and also accepts open, won, lost or deleted, Stage Name or ID keeps one stage, User Name or ID one owner, and Predefined Filter Name or ID points at a filter saved in the CRM.

Looks up deals from free text, the way the Pipedrive search bar does, and returns each match as an item.

• Term: the text to look for, at least 2 characters, or 1 when Exact Match is on. The search ignores case.
• Search Fields: title, notes or custom_fields, all of them by default.
• Return All and Limit: the usual pair when a vague term matches too much.
• Additional Fields: Organization ID or Person ID restrict the search to one account, and Include Fields adds optional data such as deal.cc_email.

Rewrites the fields of a deal already in the pipeline and touches nothing else.

• Deal ID: the card to edit.
• Update Fields: Status moves the deal to won, lost or deleted, Lost Reason records why it went nowhere, Stage Name or ID advances it, Value and Currency correct the amount, Expected Close Date pushes the date and User Name or ID reassigns the owner.

Attaches a product line to a deal, with its price and quantity, and returns the attachment that was created.

• Deal ID: the deal receiving the line.
• Product ID: the product taken from the Pipedrive catalog.
• Item Price and Quantity: the price used on this deal and how many units go on it.
• Additional Fields: Discount with Discount Type set to percentage or amount, Tax as a percentage, and Comments to describe the line.

Reads back the product lines attached to one deal, each with its price, its quantity and the attachment ID the other product operations need.

• Deal ID: the deal whose lines are read.
• Return All: on for every line of the deal; off, Limit stops the node earlier.

Detaches a product line from a deal. The product stays in the catalog, only its link to this deal disappears.

• Deal ID: the deal holding the line.
• Product Attachment ID: the ID of the deal-product, which is not the product ID. Get many products of a deal returns it, and that is the value to pass here.

Changes a line already attached to a deal: price, quantity, discount or tax.

• Deal ID and Product Attachment ID: which line to edit, using the deal-product ID rather than the product ID.
• Update Fields: Item Price and Quantity for the commercial terms, Discount with Discount Type, Tax as a percentage, and Comments for the note attached to the line.

Uploads a file into Pipedrive from the binary data a previous node carries. No download, no copy-paste in between, and the file lands on the record you point at.

• Input Binary Field: the name of the input binary field holding the file to be written.
• Additional Fields: Deal ID, Person ID, Organization Name or ID, Activity ID, Lead ID or Product ID, depending on what the document belongs to.

Removes a file stored on a Pipedrive record. The record itself stays untouched, only the attachment disappears, and the operation answers with the ID of the file that was deleted.

• File ID: the numeric ID of the file to delete.

Brings the content of a Pipedrive file back into the workflow as binary data, ready for another node to read it or store it elsewhere.

• File ID: which file to download.
• Put Output File in Field: the name of the output binary field the file lands in. The next node reads that field, so pick a name it expects.

Returns what Pipedrive knows about one file, its name and its description included, but not the binary content. Download a file is the operation that carries the bytes, so the two often run one after the other.

• File ID: the file to read.

Renames a file or rewrites what it says about itself, with no re-upload involved.

• File ID: the file to edit.
• Update Fields: Name sets the visible name of the file and Description the text shown next to it.

A lead sits in Pipedrive before any deal exists, where inbound requests wait to be qualified. The operation files one from what the workflow just collected and returns the stored record.

• Title: the name the lead is listed under, often assembled from the company name and the channel the request came through.
• Associate With: pick organization or person, and that choice decides whether the node asks for Organization ID or Person ID.
• Value: the potential amount carried by the lead, filed in Additional Fields next to Expected Close Date in YYYY-MM-DD format.

Junk piles up fast in a lead list: duplicates coming from two forms, test entries, records left behind by a workflow that misfired. This operation removes one for good.

• Lead ID: the string identifier of the lead to delete, handed over by the node that found it; the field is required, so an empty value stops the execution instead of erasing the wrong record.

Pulling a single lead by its identifier gives the workflow the version Pipedrive holds right now, not the copy an earlier step has been carrying around.

• Lead ID: the only field to fill in; the operation reads and changes nothing, which makes it safe inside a loop or on a retry branch.

The lead list comes back as one item per lead, which is how most reporting and sync workflows start.

• Return All: switched on, n8n keeps requesting pages until the last lead is in; switched off, Limit sets the ceiling.
• Archived Status: not_archived for what is still being worked, archived for what was set aside, all for both.
• Filters: cuts the read down at the source by Owner Name or ID, Organization ID or Person ID.

Only the fields opened in Update Fields travel to Pipedrive. Everything else keeps the value it had, so a workflow can pass over the same lead twice without flattening what a sales rep typed by hand.

• Lead ID: the lead being rewritten, required even when a single value changes.
• Is Archived: takes the lead out of the active list without deleting it, the usual ending for a branch that concludes there is no interest.
• Title, Value and Expected Close Date: the three fields that make a lead readable in a forecast.

Written context is what makes a CRM record usable months later. The operation writes a note and attaches it to whichever record the workflow is handling.

• Content: the text itself, the single required field, usually assembled by an earlier node from a call summary or a form answer.
• Deal ID, Person ID, Organization Name or ID and Lead ID: the record the note hangs on, all set in Additional Fields.
• Pinned to Deal: keeps the note at the top of the deal instead of letting it slide down the timeline.

Some notes are written by automation and are not meant to outlive it: a draft summary replaced by a better one, a note posted on the wrong record.

• Note ID: the numeric identifier of the note, taken from the step that listed or created it; note identifiers are numbers in Pipedrive while lead identifiers are strings, so the two cannot be swapped by accident.

When a later step has to quote a note word for word, it starts by reading it here rather than rebuilding it from memory.

• Note ID: the identifier of the note to read, a number; the operation asks for nothing else, so it slots in behind any step that already knows which note it wants.

Notes come back as a list, filtered on the Pipedrive side rather than sorted out afterwards inside the workflow.

• Filters: Start Date and End Date in YYYY-MM-DD bracket a period, while Deal ID, Person ID or Lead ID keep only the notes of one record.
• Sort: update_time puts the freshest notes first, content orders them alphabetically, id follows creation order.
• Return All: left off, Limit holds the batch down while the workflow is still being tested.

Editing a note in place beats stacking a second one underneath it, especially when a workflow refreshes the same summary after every call.

• Note ID: the note being edited, required.
• Content: the replacement text, filed in Update Fields here, where the create operation made it mandatory.
• Pinned to Person and Pinned to Organization: change where the note shows up without rewriting a word of it.

Companies land in Pipedrive as organizations, and the node creates one with a single mandatory value.

• Name: the company name, required; later searches run on it, so normalizing it before the node saves duplicate accounts.
• Custom Fields: in Additional Fields, this is where the industry, the account tier or anything else the sales team added to the object goes.
• Visible To: 1 keeps the account to its owner and followers, 3 opens it to the entire company.

Deleting an account record is rare and rarely reversible, which is why the operation belongs behind a human approval rather than on the direct output of a trigger.

• Organization ID: the numeric identifier of the organization, never the company name, so a search step usually runs first to turn one into the other.

Fetching one organization gives the workflow the account exactly as Pipedrive stores it, custom fields included.

• Organization ID: which account to read, required.
• Show Raw Field Keys: switched on, the output carries Pipedrive raw field keys and option IDs instead of readable names, which is what a mapping step towards another tool usually needs.

The whole account list leaves Pipedrive in one go, which is where exports, audits and enrichment runs begin.

• Return All: on, the node chains the API pages by itself; off, Limit decides how many organizations come back.
• Predefined Filter Name or ID: reuses a filter already built inside Pipedrive, so the selection logic stays where the sales team maintains it.
• First Character: a single character that keeps only the organizations whose name starts with it, handy to split a heavy export into alphabetical batches.

Searching beats listing when the workflow holds a name and needs the matching account, for instance to avoid creating the same company twice.

• Term: the text being searched, two characters minimum, or a single character when Exact Match is on.
• Exact Match: returns only full matches of the term, without paying attention to case.
• Search Fields: restricts the search to name, address, notes or custom_fields; left empty, all of them are searched.

Account data ages quickly: a rename after an acquisition, a new owner, a tier that moved. This operation writes those changes onto the existing record.

• Organization ID: the account being edited, required.
• Name and Owner Name or ID: both sit in Update Fields, so sending one of them leaves the other untouched.
• Use Raw Field Keys: lets the workflow address custom fields by their Pipedrive keys and option IDs rather than by readable names, which holds up better when labels change.

Contacts live in the person object, and the node creates one from a name, with everything else left optional.

• Name: the contact name, the only required field.
• Emails and Phones: collections rather than plain text fields, because a contact can carry a work address and a personal one, a landline and a mobile.
• Organization Name or ID: attaches the contact to an account right away, so nobody has to link them by hand afterwards.

A contact who asks to be removed, or a duplicate created by two integrations at once, leaves the base through this operation.

• Person ID: the numeric identifier of the contact to delete, most often resolved a step earlier by a search on the email address.

A single contact comes back, read by its identifier, with the fields the sales team keeps up to date on it.

• Person ID: the contact to read, required.
• Show Raw Field Keys: returns Pipedrive raw keys and option IDs in place of the readable labels, useful when the next node expects stable keys.

A sync, a segmentation or a hunt for missing email addresses all start the same way, by reading the contact base in bulk.

• Return All: on, every contact comes back page after page; off, Limit keeps the run short while the workflow is being tuned.
• Filters: Predefined Filter Name or ID reuses a filter saved in Pipedrive, and First Character keeps only the contacts whose name starts with the letter given.

When the workflow knows an email address but not the Pipedrive person ID, this search closes that gap.

• Term: the text to match, at least two characters, or one once Exact Match is on.
• Search Fields: email, phone, name, notes or custom_fields. Narrowing to email alone skips namesakes fast.
• Organization ID: keeps only the contacts of one account.
• Include Fields: pulls in extras the default response skips, such as person.picture.

Phone numbers change, people move to another company, labels get reworked. The operation applies those corrections to a contact already in the base.

• Person ID: the contact being edited, the only required field.
• Emails and Phones: sent as collections, so the contact can hold several addresses and several numbers.
• Visible To: 1 for the owner and followers, 3 for the entire company.

One required field is enough to push a new product into the Pipedrive catalog. The rest of the record travels in an optional collection.

• Name: the label reps read when they attach the product to a deal; the node will not run without it.
• Additional Fields: holds Code for the internal reference, Unit for the selling unit, Tax for the tax percentage, Prices for the amounts and Owner ID for the user who owns it.
• Visible To: 1 keeps the product private to its owner and followers, 3 shares it with the whole company.

Removing a product from the catalog is a one-parameter call. The node works on the numeric identifier of the record and never on its name, so the value comes from a step that located the product first.

• Product ID: the number of the product to delete, usually {{ $json.id }} handed over by a search or a list placed upstream.

Reading a single product hands its fields to the rest of the workflow. That is how a quote or an internal alert ends up with the unit and the tax stored in the catalog instead of a value typed from memory.

• Product ID: which record to read, as a number; an expression such as {{ $json.product_id }} pulls it from the previous node.
• Show Raw Field Keys: off, the output uses human-readable names; on, it returns raw Pipedrive field keys and option IDs, which suits a script running next.

Get Many returns the products of the account, one item per record, with no filter to fill in. The volume is the only thing left to decide.

• Return All: ticked, n8n walks the pages of the API until the last product; unticked, Limit caps how many records come back.
• Show Raw Field Keys: the same switch as on the single read, applied to every item of the list.

Search matches on text rather than on an identifier. It bridges a product name written by hand, in a form or an email, and the record the workflow acts on.

• Term: the text to look for, two characters at minimum, or a single one when Exact Match is on.
• Exact Match: only full matches of the term come back, and the comparison ignores case.
• Search Fields: narrows the search to name, code or custom_fields, all three being queried by default; Include Fields adds optional fields to the results.

An update sends only the fields placed in Update Fields. Correcting a price therefore leaves the code, the unit and the ownership of the record exactly as they were.

• Product ID: the record to edit, identified by the number Pipedrive gave it.
• Update Fields: takes the same attributes as the creation, Name included, which becomes optional here since a rename is not always wanted.
• Use Raw Field Keys: turn it on when the incoming values already use raw Pipedrive field keys and option IDs rather than human-readable names.