Pipedrive audit log: how to see who changed what

Pipedrive has no account-wide log of record edits. To see who changed a deal, person or organization, open the record and go to History > Changelog: each entry shows the field, the old and new value, when, and who made the change. Developers can pull the same history through the API. The Security dashboard's audit log, on Ultimate only, covers security events for the past two months, not field edits. For deletions, Tools and apps > Restore data shows who deleted each item and when, for 30 days. The big gap: none of them says a merge happened.

Changelog, flow and recents endpoints, token costs and deletes tested through the API in a Pipedrive sandbox on November 3, 2026, along with the history of merges we made in October and November. Restore data checked on screen on November 2, 2026, with an admin and a regular user, and the Changelog tab on November 2 and 3, 2026. Security dashboard and alerts details from Pipedrive's help center; we didn't test them. Last checked: November 3, 2026. What we couldn't verify.

Where to look, by question

How to see who changed a deal, person or organization

Pipedrive's detail view article (updated September 3, 2026) says each deal, person and organization has a Changelog tab under History, listing changes since the record was created, sorted by date and time, including default and custom fields.

1. Open the deal, person or organization.

2. In the History section of the detail view, click Changelog.

3. Read the entries, sorted by date and time. Each one shows the field, the old and new value, the time, and the user with the source in brackets, for example "(API)" for a change made by an integration. The other History tabs filter notes, activities, emails, files, documents and invoices; they're not part of the changelog.

For deals, the deal detail view article (updated October 12, 2026) lists stage, value, label, contact, expected close date and default and custom fields. It doesn't mention the owner, but in our test an owner change was recorded too (we read it through the API).

Neither help page says the Changelog tab shows who made each change or the old and new values, but it does. On November 3, 2026, a test deal changed through the API showed entries such as Status, from Open to Deleted, with "Today at 11:13 AM" and the user followed by "(API)". A deleted deal keeps its Changelog tab too.

The Security dashboard audit log (Ultimate)

This is the screen most people mean by "Pipedrive audit log", and it's about security, not deals. Pipedrive's security dashboard article (updated September 30, 2026) puts it at Company settings > Security center > Dashboard.

• Audit log: "every security-related change" over the past two months, with User, Event, Type and Time columns. You can filter it and export it to a spreadsheet.
• Device history: logins over the past two months, with user, device, location or IP, login and logout.
• Active devices: who is signed in where.

The audit log, active devices and device history are Ultimate only. On Lite and Growth, the dashboard shows the users logged in, a one-week overview and a security assessment (security features article, updated September 3, 2026). Only users with account settings access can open the dashboard, and they get a monthly summary email.

The help never says the audit log records field edits on deals or people. Treat it as a log of logins and security events, and use the Changelog tab for record edits.

Security alerts

Settings > Security center > Alerts emails admins, instantly or in a daily or weekly digest, when (security alerts article, updated September 3, 2026):

• someone logs in from a new device or location
• a new user is invited
• a user has more than 3 failed logins in a row, or requests a password reset
• someone downloads an export of deals, organizations, people, activities or notes
• a pipeline, stage or custom field is deleted
• one user deletes more deals, people or organizations than a threshold the admins set, which applies to the whole company

The alert history sits in Security dashboard > Audit log > Alerts. The alerts article says the feature is for "Enterprise plans"; the security features article says Ultimate. We couldn't check the pricing page.

Restore data: the log of deletions

Pipedrive's Restore data article (updated September 3, 2026) says every user can open Tools and apps > Restore data. It shows items deleted in the last 30 days, and each item's details show who deleted it, when, and the deletion source. On Lite and Growth, users can restore any item they can see; on Premium and higher, their own items, or other users' items they can see and edit.

In our sandbox, a regular user restored items an admin had deleted, and a bulk delete showed up as "Bulk deletion" by the admin.

Two things the help doesn't mention:

• A deleted record keeps its changelog. On screen and through the API, the changelog of a deal we deleted still answered, and gained a status change from open to deleted and a close_time, with the user and the source.
• There's a Bulk edits tab, and Revert works. In our November 2026 test, a list-view bulk edit appeared there and reverted. Records edited one at a time through the API did not appear. Single edits, from the screen or the API, have no revert.

More on what comes back and what doesn't in our backup and Restore data guide, and on who can delete and restore in how to bulk delete.

Getting the change history through the API

For admins and developers, or an AI that reads Pipedrive for you. The endpoints are on Pipedrive's Deals, Persons, Organizations and Recents reference pages, which carry no update date (checked November 3, 2026).

Another process was using the sandbox at the same time, so a few readings came out higher than the spec. For daily budgets, see why Claude used up your Pipedrive API tokens.

What a /changelog entry contains, measured (the reference pages don't document the response):

• field_key, old_value, new_value and time. Time is UTC, as YYYY-MM-DD HH:MM:SS with no time zone.
• actor_user_id: the user who made the change. In our test it was the token owner on every entry, including the change of owner to another user.
• change_source and change_source_user_agent: we saw api for our script, app for changes made on screen with the browser's user agent, and import-service for records created by an import. The webhooks v2 guide (updated July 28, 2026) only documents app and api; import-service isn't documented anywhere we found.
• is_bulk_update_flag.
• Custom fields appear by their 40-character key, without the field's name. Phones and emails come as the whole list before and after the change.

In our test, the deal changelog recorded the value (100 to 250), the owner, a custom text field, the title and the linked person. The person changelog recorded the name and the phone. /flow returned the same changes with formatted old and new values (the owner's name instead of an ID).

There's no v2 version: GET /v2/deals/{id}/changelog returned 404 "No routes found". None of these endpoints is in the 58 v1 endpoints Pipedrive deprecated (posted April 14, 2025, effective January 1, 2026), and all still answered in November 2026. More in API v1 deprecated.

Webhooks v2 for a trail going forward

The changelog only shows the past. To record changes as they happen, webhooks v2 send meta.user_id (who triggered the event), change_source, is_bulk_edit, and previous: the changed fields on a change, the whole last state on a delete. On a merge, the absorbed record's delete carries merged_to_id, and the kept record's change, when there is one, carries merged_from_id. Pipedrive retries 3 times (after 3, 30 and 150 seconds), bans the webhook for 30 minutes after 10 failed first attempts and drops events meanwhile, and deletes a webhook after 3 days without success. So keep a periodic check against the API. Details in our webhooks v2 guide.

What the history doesn't show

Merges are the hole. Pipedrive's merge dialog says what moves, but afterwards nothing in the history of the kept record says a merge happened. The side effects can surface elsewhere without the word merge: in our sandbox, deals whose contact person changed in a manual merge showed up in Restore data's Bulk edits tab. Webhooks v2 are the only place that marks a merge. What a merge loses, and what you can't undo: how to merge duplicates.

/v1/recents isn't a log either. It returns a snapshot of each changed record, with no field, old value or user, and a record edited seven times appears once. It does tell you what was deleted since a given time: after our deletes, the deal came back with deleted: true and the person with active_flag: false.

Common mistakes

• Looking for an account-wide audit log of edits. Pipedrive documents none. The Ultimate audit log is for security events.
• Trusting change_source as the origin. In an API merge, the notes and activities it moved arrived in webhooks as app with is_bulk_edit: true, and a lead merged through the API sent its delete as app. Use it as a hint, not proof.
• Expecting a merge in the history. On the kept record it's invisible; on the absorbed one it looks like a delete.
• Using /recents as a diff. It's the current state, not the change.
• Assuming a single edit can be undone. Single edits, from the screen or the API, have no revert. List-view bulk edits do, in Restore data. For single edits, the changelog shows the old value and someone has to type it back.

What we couldn't verify

• How far back the changelog goes. Pipedrive documents no retention; our oldest entries date from when the sandbox started, October 14, 2026.
• Which plans include the Changelog tab and the changelog endpoints. The pages we read don't name one.
• What the organization changelog returns and what it costs. It's documented; we didn't call it.
• Anything on the Security dashboard, audit log or alerts. We didn't check the sandbox's plan or test them, including whether the audit log lists record edits or bulk deletes.
• Which plan has security alerts: one help page says Enterprise, another Ultimate. The pricing page didn't load for us.
• Whether workflow automations, Marketplace apps or OAuth apps show their own change_source or user agent. We only used an API token.
• How changes to leads' fields are tracked, if at all.
• Exporting the changelog. No native export is documented; only the API gives it to you. The audit log and device history export to a spreadsheet, per the help.
• The real token cost of the followers changelog (spec 10, one noisy reading of 50).

Where Pipehand fits

Pipehand is in development as a replacement for Pipedrive's MCP, with early access for founding members from January 2027. It's designed to keep a history of every change to your Pipedrive, using webhooks, including merges and edits made by hand in the app, so a merge will leave a record of which records went into which.

If you want a full history of your Pipedrive, merges included, join the waitlist on pipehand.com.

FAQ

Does Pipedrive have an audit log?

Yes, but only for security, and only on Ultimate: Company settings > Security center > Dashboard has an audit log of security events and a device history for the past two months. Edits to deals, people and organizations are in each record's Changelog tab instead.

How do I see who changed a deal in Pipedrive?

Open the deal and go to History > Changelog. Each entry shows the field, the old and new value, when it changed, and the user, with the source in brackets, such as "(API)". Developers can get the same through GET /v1/deals/{id}/changelog.

How do I see the change history of a contact in Pipedrive?

Open the person or organization and click Changelog under History. Through the API, use /v1/persons/{id}/changelog or /v1/organizations/{id}/changelog. Leads have no changelog.

Which Pipedrive plan has the audit log?

The Security dashboard's audit log, device history and active devices are Ultimate only. Lite and Growth get a reduced dashboard with the users logged in, a one-week overview and a security assessment.

How far back does the Pipedrive audit log go?

The security audit log and device history cover the past two months. Pipedrive doesn't document how long the record changelog is kept.

Can I see who deleted a deal in Pipedrive?

Yes, for 30 days: Tools and apps > Restore data shows who deleted each item, when and from where. In our test, the deleted deal's changelog also kept the delete, with the user and the source.

Does Pipedrive track merges in the history?

No. In our sandbox the kept record's changelog showed nothing about the merge, and the absorbed record looked like an ordinary delete. Only webhooks v2 mark a merge, with merged_to_id and merged_from_id.

Is there an API for Pipedrive change history?

Yes: GET /v1/deals/{id}/changelog, /v1/persons/{id}/changelog and /v1/organizations/{id}/changelog, documented at 20 tokens per call. There's no v2 version, and they weren't part of the v1 deprecation.

Can I undo a change in Pipedrive?

Deletions, for 30 days, from Restore data. List-view bulk edits, from the Bulk edits tab of Restore data, which worked in our November 2026 test. An import, within 48 hours, by a global admin from the import history. Single edits and merges, no; the changelog shows the old value so you can type it back.