Zoho CRM integration
Pipemetry reads your Zoho deals and their change history and turns them into a forecast you can explain: point-in-time pipeline history, transparent forecast models, accuracy tracking, and risk alerts.
Zoho runs in several regions — zoho.com, zoho.eu, zoho.in, zoho.com.au, zoho.jp. You tell Pipemetry which one your CRM lives in, because credentials issued in one region do not work in another.
Create a Self Client in the Zoho API Console and paste the client ID, secret and refresh token. Pipemetry needs read access to your deals, their change history and your stage settings. It never writes to Zoho.
Pipemetry imports your deal history on connect and tells you the date that history actually begins, so you can see exactly which part of the chart is evidence and which is not.
Pipemetry reads each deal’s timeline and Zoho’s own stage-history records, and builds a point-in-time event log. It can reconstruct what your pipeline looked like on a historical date rather than only today — what slipped, what pulled in, what changed since last week.
Zoho records what a field changed from as well as to. That is more than some CRMs expose, and it means Pipemetry can show a real before-and-after for an amount or a stage move rather than inferring one.
Pipemetry reads your Zoho stage list — including which stages you have marked as won, lost or open, and your own forecast categories. Your configuration decides how deals are grouped; Pipemetry does not pattern-match your stage names.
A deal nobody has edited has no change history, and Pipemetry says so instead of pretending otherwise. Every chart reports the date from which its history is real, so a thin import reads as a young pipeline rather than a broken import.
Read access to your deals, their change history and your CRM settings. Pipemetry never writes to Zoho — it never creates a record and never changes a stage. One thing worth knowing: Zoho grants CRM access per module rather than per operation, so the Self Client you create is broader than what Pipemetry uses. You create it yourself and can revoke it in the Zoho API Console at any time.
No. Pipemetry polls Zoho on a schedule and imports changes since the last successful sync. Your forecast is as current as the last import, and the app shows when that ran rather than implying live streaming.
As far back as your own Zoho records go. Zoho keeps a per-deal timeline and stage-history records, and how much exists depends on your org and how long deals have been edited there — it is a property of your account rather than of Pipemetry. Pipemetry reports the date its evidence actually begins instead of assuming a window.
All of them: zoho.com, zoho.eu, zoho.in, zoho.com.au and zoho.jp. You pick your region when you connect. This matters because Zoho credentials are bound to one region and fail against another in a way that looks like a wrong password.
It is written to be economical: most of the stage history comes from a single bulk read rather than a call per deal, and the sync backs off when Zoho asks it to. The initial import is the heaviest moment; routine syncs only fetch what changed.
Your Zoho credentials are encrypted at rest and never returned by the API once saved. Deal data is stored per workspace with database-level tenant isolation, and disconnecting removes the stored credentials.