Revenue forecasting and pipeline analytics for Pipedrive.

Read access to your deals and their change history. A personal API token is not a read-only credential — it follows the connecting user’s own permissions — so if you want the grant itself bounded, use OAuth, which needs the deals and recents scopes — deal history lives under the recents scope, not the deals scope, so a token with deals access alone can read your pipeline but not its history — plus the contacts scope (contacts:read), so Pipemetry can count the people on each deal; it keeps only that number, never a name or email. Without it your pipeline still imports, but the single-threaded-deal alert cannot run. Pipemetry reads your deal data and never creates or changes a deal, and stored credentials are encrypted at rest. The one thing it writes to your account is a webhook subscription, and only if you switch on real-time updates — removed again when you switch them off.

It can be. By default Pipemetry polls on a schedule — it looks for deals changed since the last run, reads just their changelogs, and advances a watermark. You can also switch on real-time updates: Pipemetry registers a webhook subscription in your Pipedrive account, and Pipedrive then pushes each deal change the moment it happens, using none of your API budget for the changes it delivers. That subscription is the only thing Pipemetry writes to Pipedrive, and switching real-time updates off removes it. That option needs an admin connection: Pipedrive only delivers webhooks for deals the connecting user can see, so a non-admin connection would silently miss part of your pipeline — Pipemetry checks and tells you rather than turning it on anyway.

As far back as your Pipedrive account’s deal changelog goes — that retention is a property of your account, not of Pipemetry, and it varies. Rather than guess, Pipemetry reports the date your observed history actually begins after the first backfill. Before that date it has no recorded changes to reconstruct from, and it says so instead of drawing a flat line that looks like data.

Yes, more than most integrations. Pipedrive applies visibility per deal, so a non-admin connection can silently see fewer deals than your account holds — with no error anywhere. Pipemetry checks whether the connected identity is an admin and warns you when it is not, because a forecast built on a subset of your pipeline looks perfectly healthy from every other angle. Connect with an admin identity if you want whole-pipeline coverage.

Pipedrive’s daily token budget is shared across every integration you run, so Pipemetry caps itself at a fraction of your account’s budget and paces its reads against the rate-limit headers Pipedrive returns. It is designed to leave room for the rest of your stack rather than consume the day’s allowance in one sweep.

Pipemetry enforces tenant isolation at the database layer with row-level security, encrypts data in transit, encrypts your credentials and backups at rest, and keeps a WORM (write-once) access audit. SOC 2 is in progress. See the security page for detail.