Check what synced to and from Pipedrive

Audience: operators & admins · Scope: the Pipedrive Change Log screen · Last reviewed: 2026-07-22

What this does — Every time a value moves between a website quote and its Pipedrive deal — in either direction — the site writes it down: what changed, when, which way, from what to what. The Pipedrive Change Log screen is where you read that, and it opens with a summary telling you whether the sync is healthy right now.

Use it to answer "did that actually go across?", "who changed this — us or Pipedrive?", and "is anything stuck?".

Before you start

• Nothing to switch on. The log records itself, always, and has done since the sync went live.
• Nothing here changes anything. It is a read-only record — you cannot edit or delete entries, and editing one wouldn't change the quote or the deal anyway.

Find it

Diagnostics → Pipedrive Change Log in the ConfigBox admin menu.

Using it

The health summary (top of the screen)

Three panels, read left to right:

• Change log — how much moved in each direction in the last 24 hours and 7 days, how many distinct quotes were involved, and how long ago the last change was in each direction. If "Last outbound change" says 3 days ago on a busy week, something has stopped.
• Outbound (quotes → Pipedrive) — what's waiting to go out:
  • Queued — normal. These go on the next scheduled run (every minute).
  • Retries exhausted — tried and failed repeatedly; left alone until the quote changes again.
  • Stalled — scheduled against an older revision of a quote, so the sync will never pick them up on its own.
  • Linked deals — how many quotes currently point at a Pipedrive deal.
• Inbound webhook queue — changes arriving from Pipedrive: Pending (waiting, normal, should clear within a minute) and Failed (kept for inspection).

A tile turns red when it holds something worth a look — retries exhausted, stalled, or failed. Hover any tile for a one-line explanation.

The table

Newest first. Filter with the boxes above it — they combine, and the site remembers your choices:

Filter	Use it to
Logged (UTC)	Narrow to a date — type 2026-07-22 for one day, or 2026-07 for a whole month
Direction	In = Pipedrive changed the quote · Out = the site changed the deal
Quote serial	Follow one quote (e.g. AAE8677)
Deal ID	Start from the Pipedrive side
Field	Watch one field, e.g. type stage or value

The newest entries are always on top, so "what happened recently?" needs no filter at all.

Long values are shortened in the table — hover to see the whole thing, or click the row's ID to open it and read the old and new values in full.

What happens next

Nothing — reading this screen doesn't trigger anything. To get a stuck quote moving again, make any change to the quote and save it: that re-schedules it and clears the failure count.

Good to know

• Times are UTC, not local — the same clock for both directions so entries line up. The summary also says things like "12 minutes ago", which is usually what you want.
• "No entries" for a push is normal. Outbound entries are only written when a field really changed on the deal. If the deal was already up to date, the sync ran and correctly wrote nothing.
• A brand-new deal shows its first values with the "old value" column empty.
• Statuses show their proper names, not internal codes.
• Old entries are tidied up automatically. By default the log keeps 4 weeks; anything older is deleted overnight. You can change that under Custom Settings → Pipedrive Integration → Change log retention (weeks). Setting it to 0 keeps everything forever — only do that deliberately, because the log then grows without limit. The summary's "rows in total / oldest" line is how you see the effect.
• Deleting is permanent. Once entries pass the retention window they're gone, so if you need a longer history for an audit, raise the setting before the entries age out.
• Red tiles are a prompt, not an alarm — a single failed queue item usually sorts itself out on the next change. Persistent or growing numbers are worth reporting.

Screens and labels can differ slightly between environments — if a label doesn't match what you see, check with your Beta-Calco contact.

If the connection itself looks broken

The change log tells you what did sync. When the answer is "nothing, for a while", the question becomes whether the account still has what the website needs — a deleted custom field or a removed webhook stops the sync without any error the change log can show you. ConfigBox → Diagnostics → Pipedrive Provisioning checks exactly that, and puts back anything missing.

For developers → docs/pipedrive/admin-manual.md §5.