How to bulk edit in Pipedrive (and safely with AI)

To bulk edit in Pipedrive, open the list view, filter the records, select them, pick a field in the bulk edit panel and confirm. Before you confirm, check the "Run automations" option: it's on by default, so your automations fire on every record you change. An AI can't do this in one step. Pipedrive's official AI connector (its MCP server) changes one record per request, with no preview of the whole set and no undo of its own, so the AI route is for changes the list view can't express, done in small, checked batches.

Tested in a Pipedrive sandbox, October 2026. Last checked: October 29, 2026. What we couldn't verify.

Which way to bulk edit

What you want to change	Best way today (October 2026)
One field to the same value on many deals, people or orgs	List view bulk edit
A different value on each record (a new region per country)	Export with the ID column, edit the spreadsheet, import it back as an update
A lead's custom fields	Not in the leads bulk edit panel. One lead at a time, by hand or with an AI
A change that needs judgment on each record ("tag every deal whose notes mention a competitor")	An AI, in batches of 50 to 100, after the checks below
The same cleanup every week	Zapier, Make or a tool such as Insycle, with a small test first
Add a follow-up activity to many deals	Bulk add activities in list view, up to 100 per selection (Growth plan or higher)

How to bulk edit in Pipedrive, step by step

You need the Bulk edit items permission (Global permissions > Data management). Admins have every permission; if a regular user doesn't have it, an admin can turn it on in their permission set.

Open the list view of what you want to change: Deals, Contacts (people or organizations), Leads Inbox, Activities, Products or Projects. If you're in the pipeline view, switch to list.
Click the filter menu at the top right and pick or create a filter that matches exactly the records you want. Check the count it shows.
Select the records. The bulk edit panel opens.
In the panel, find the field, click Edit current value and choose the new value.
Before you confirm, look at Run automations. Untick it if the change shouldn't send emails, create activities or move deals through your automations. If you don't see the option, ask an admin, or turn the automation off in Automations while you make the change.
Click Edit to confirm.

What each list can change, from Pipedrive's bulk edit guide (updated September 3, 2026):

List	What you can bulk edit
Deals	Owner, pipeline and stage, status, value, labels, close date, custom fields and more
People, organizations	Owner, labels, visibility, their standard fields and custom fields
Products	Owner, visibility, their standard fields and custom fields
Leads	Title, labels, value, owner, visibility, source channel. No custom fields
Activities	Subject, assignee, type, done, due date, linked records, priority

The guide doesn't state a maximum number of records per bulk edit.

Can you undo a bulk edit in Pipedrive?

Maybe, within 30 days. Pipedrive's product updates list "Revert bulk changes with confidence" in March 2026: a page in Tools and apps > Restore data where you can see and revert bulk edits, lead-to-deal conversions included. Our sandbox's Restore data page had Bulk edits and Bulk conversions tabs on October 14, 2026. But the bulk edit guide still says changes "can't be undone after confirmation", no help article describes the revert, and we haven't run one yet. Treat it as an untested backup, not a reason to skip the export.

To see what changed on a record, open it and go to History > Changelog.

When each record needs a different value: the spreadsheet route

Pipedrive's update with a spreadsheet guide (updated September 3, 2026) works like this: add the ID column to your list view, export, change the values in the file without touching the ID, then import it and map the ID column. Pipedrive updates the records whose ID matches instead of creating new ones.

It needs the import permission. That guide caps update files at 50,000 rows; the general import guide (updated October 19, 2026) says 200,000.
A global admin can revert an import for 48 hours. Pipedrive doesn't say whether that restores the old values of updated records, so keep your export.
Most imports don't trigger automations, except date-based ones when you change a date field. If automations shouldn't react, the import is the quieter route.

What happens when you ask an AI to bulk edit

People already do it: in August 2026 a Claude user on r/CRM wrote that the assistant read notes from 40+ deals and "bulk-tagged every person record".

Pipedrive's API has no bulk update for records. It updates one deal, person, organization or lead per call (public API specs, checked October 29, 2026). Pipedrive told developers in 2020 that bulk updates were "in the roadmap, but no ETA".
The official connector follows the API. Of its 51 tools (list, updated October 22, 2026), the update tools change one record per call and none is a bulk tool. 300 deals means 300 calls, and each change is saved the moment it's made. More in what Pipedrive's MCP can and can't do.
No preview, no "Run automations" option, no undo. The AI shows its plan if you ask, but nothing stops it from writing record 1 before you've seen record 300. Pipedrive doesn't say whether its bulk edit revert covers changes made this way.
A failure leaves a half-done job. If your daily API budget runs out or the chat stops, some records are changed and some aren't.

Zapier and Make work the same way: one update per record.

What it costs in API tokens

Pipedrive counts each API request in tokens, and every company gets a daily allowance shared by all its integrations, web forms included. Community MCP servers, Zapier and Make spend it. Pipedrive's official connector is "subject to token limits based on your plan" (MCP page) without saying whether it's the same allowance. Here is the same change to 1,000 deals at API costs:

How the AI finds the deals	Approximate tokens
From one saved filter: 2 lists of 500, then 1,000 updates (costs we measured)	2 × 10 + 1,000 × 2 = about 2,000
Searching deal by deal, then reading and updating each (Pipedrive's general costs: 40, 2, 10)	1,000 × 52 = 52,000

Measured in our sandbox in October 2026: a v2 list of 500 records cost 10 tokens and a v2 update about 2. The second row is more than a one-seat Lite account gets in a day (30,000). The budget per plan and the reset time are in why Claude used up your Pipedrive API tokens.

How to bulk edit with AI safely today

Connect your AI to Pipedrive (Claude, ChatGPT) and run every bulk job like this:

Filter first, in Pipedrive. Build a filter that returns exactly the records to change.
Export a copy. Export that list with the ID column and every field you're changing (it needs the "Export data from list views" permission). It gives the AI the IDs, and with the spreadsheet route above it's how you put values back.
Give the AI the IDs, not names. Paste the ID column, or name the saved filter if your connector can use it. Searching record by record costs about 25 times more (table above).
Ask for a count and a sample, then stop. The AI should confirm how many records it will change and show the first 10 with the current and new value, before writing anything.
Test on 5 records. Check them in Pipedrive: right field, right value, nothing else touched.
Decide about automations. There's no option to skip them on this route. If an automation fires on the field you're changing (a stage change that emails the client), turn it off in Automations for the run and back on after.
Run in batches of 50 to 100, right after your daily budget resets (07:00 UTC in our test), and tell the AI to stop at the first error.
Check the result. Filter the list for the new value and compare the count, and open a few records' History > Changelog.

Prompts to copy

Prompt	What it prevents
"Here are the IDs of the deals to change: [paste IDs]. Don't search or read anything else. Tell me how many and stop."	Expensive searches, wrong set
"Show the first 10 as a table: name, current [field], new [field]. Don't change anything until I say go."	Writing before you've seen the change
"Change only these 5 IDs: [IDs]. Then stop so I can check them in Pipedrive."	A bad rule hitting every record
"Now do the next 50 from the list. Update only [field]. If any call fails, stop and tell me which IDs were done."	Half-done jobs you can't trace
"Don't retry a failed call more than once. Before each batch, tell me how many records are left."	Retry loops that burn the budget

Common mistakes

Selecting all without checking the filter's count, in the list view or in the AI's answer.
Asking the AI for "all deals from Spain", so it searches and reads hundreds of records before the first change.
Believing "Done, I updated all 300" without filtering for the new value. An AI that hit an error halfway can still sound finished.
Running a big AI job in the middle of a working day. If it uses your API budget, a mistake can block your web forms until the next reset.

What we couldn't verify

Which fields Pipedrive's bulk edit revert restores, who can use it, and whether it covers changes made through the API.
Whether a regular user sees the "Run automations" option.
Whether an update through the API fires update-triggered automations.
What each official MCP action costs and whether it uses the API budget.

Where Pipehand fits

Pipehand is planned to launch in April 2027 as a replacement for Pipedrive's MCP. Your AI will ask for one bulk edit on a filter, and before writing Pipehand will show how many records change, with examples. Above 50 records (a threshold you can change) it will wait for a person to approve with a click in the web app or an email, which the AI can't do for you. It's designed to run the change in batches that respect your daily API budget and to keep a copy, so you can undo the whole edit as one operation.

If you want your AI to bulk edit Pipedrive with a preview, an approval and an undo, join the waitlist on pipehand.com.

FAQ

How do I bulk edit in Pipedrive?

Open the list view, apply a filter, select the records, choose a field in the bulk edit panel, click Edit current value, pick the new value and confirm with Edit. Check "Run automations" first: it's on by default. You need the Bulk edit items permission, which an admin can turn on.

Can I undo a bulk edit in Pipedrive?

Maybe. Pipedrive's March 2026 product update says you can revert bulk edits within 30 days from Tools and apps > Restore data. Its bulk edit help article, updated September 3, 2026, still says changes can't be undone. Export the records before a big edit either way.

Does the Pipedrive API have a bulk update endpoint?

No, not for deals, people, organizations or leads as of October 29, 2026. Each record is one update call, so 1,000 deals means 1,000 calls against your daily API budget. The only multi-item writes are for products on one deal, a field's options, and deleting several custom fields or filters.

Can Claude or ChatGPT bulk edit Pipedrive?

Yes, with limits. Through Pipedrive's official connector they can change many records, but one per call, with no preview of the whole set and no undo. For one field on many records, use Pipedrive's own bulk edit. For the rest, export first, give the AI the IDs, test on 5 records and run in batches.

How many records can I bulk edit at once in Pipedrive?

Pipedrive's bulk edit guide doesn't give a limit. Updating with a spreadsheet allows up to 50,000 rows per file, and bulk adding activities is capped at 100 per selection. For a very large change, test on a small filter first.

For developers

Endpoints, costs and limits for a bulk job

No bulk record update: v2 has PATCH /api/v2/{deals|persons|organizations}/{id} only (x-token-cost 5 in the OpenAPI spec; we measured about 2). Lead updates are v1 only: PATCH /v1/leads/{id}, cost 10. Multi-item writes that exist: POST /api/v2/deals/{id}/products/bulk and DELETE /api/v2/deals/{id}/products (up to 100), the *Fields/{field_code}/options endpoints, and v1 DELETE /v1/{deal|person|organization|product}Fields?ids= and DELETE /v1/filters?ids=.
Selecting the set: v2 lists take filter_id, or ids with up to 100 IDs, and limit up to 500. At the spec's v2 costs (list 10, update 5) the 1,000-deal job is about 5,000 tokens. v2 search costs 20 in the spec and 40 in the general docs, with its own burst limit of 10 per 2 seconds.
Burst: we measured 20 requests per 2 seconds with an API token and 80 with OAuth on the same account; the daily budget was the same with both. Zapier's loop runs up to 500 iterations, all "in parallel" (help article, May 29, 2026), so a large loop can hit the burst limit.
Automations: the API has no documented flag to skip them.