Zoho Books and Pipedrive integration

What moves between them

The integration flows bidirectionally. Zoho Books contacts flow into Pipedrive as organizations (for customer accounts) and persons (for individual contacts). Invoice totals flow from Zoho Books into Pipedrive deal records as custom fields, updated each time an invoice is created or modified in Zoho Books. Pipedrive organizations can be pushed back to Zoho Books to create or update contacts, maintaining alignment between systems. Webhook events from Zoho Books trigger immediate syncs; changes in Pipedrive are synced on a configured schedule.

How ml-connector handles it

ml-connector stores the Zoho Books OAuth2 refresh token encrypted and refreshes the access token proactively at 55 minutes to avoid token expiry mid-request. It routes all Zoho Books API calls to the correct regional base URL (determined by the region field in the token response) and includes the organization ID as a query parameter on every call, as required. For Pipedrive, it tracks the token budget and backs off when approaching daily limits, returning a 429 response to allow the queue to drain. Custom fields in Pipedrive are resolved by reading the field definition list (/v1/dealFields, /v1/personFields) on startup and cached in memory. The integration maps Zoho Books contact_type (customer or vendor) to determine whether a contact becomes a Pipedrive organization or person. Invoice amount and date flow into configurable custom fields on matching Pipedrive deals. Both systems support webhooks, so Zoho Books changes trigger immediate syncs while Pipedrive organization updates are pulled on a schedule. HMAC signature verification is performed on all incoming webhooks from both platforms.

A real-world example

A mid-market B2B SaaS company uses Zoho Books for invoicing and accounting, and Pipedrive for sales pipeline management across three regions (US, EU, and India). The sales team needs to see invoice amounts and payment status alongside deal records in Pipedrive, and the finance team needs customer contact information to stay synchronized. Before the integration, each sale closed in Pipedrive required manual lookup in Zoho Books to find the customer contact record, and deal totals had to be manually entered into Pipedrive as notes. New customers added by the sales team in Pipedrive had to be duplicated in Zoho Books by finance. With Zoho Books and Pipedrive connected, customer records sync automatically in both directions, invoice amounts appear as fields on every deal, and the sales team can see at a glance which deals have been invoiced and when payment is expected.

What you can do

• •Sync Zoho Books contacts bidirectionally to Pipedrive organizations and persons, keeping customer and vendor lists in agreement.
• •Push Zoho Books invoice amounts and dates into Pipedrive deal records as custom fields, visible to the sales team in real time.
• •Handle Zoho Books regional base URLs, OAuth2 token refresh with 1-hour expiry, and organization ID routing on every call.
• •Respect Pipedrive token budget and burst rate limits, with backoff and retry when approaching daily or per-second thresholds.
• •Verify HMAC signatures on webhooks from both Zoho Books and Pipedrive, with full audit trail on every sync.

Questions

How does the integration handle Zoho Books regional base URLs and OAuth2 tokens?

ml-connector stores the OAuth2 refresh token encrypted and refreshes the access token proactively at 55 minutes to avoid expiry during a request. All API calls are routed to the correct regional base URL determined by the region field returned in the token response. The organization ID is included as a required query parameter on every call to Zoho Books.

Which direction do contacts and invoices flow between Zoho Books and Pipedrive?

Contacts flow bidirectionally. Zoho Books contacts are synced to Pipedrive as organizations (for customer accounts) or persons (for individual contacts), and Pipedrive organizations can be pushed back to Zoho Books to create or update contacts. Invoice amounts flow from Zoho Books into Pipedrive deal records as custom fields, updated whenever an invoice is created or changed.

How does the integration handle Pipedrive token budgets and rate limits?

Pipedrive enforces a daily token budget based on plan (30,000 base tokens multiplied by a plan-specific multiplier) and burst rate limits per 2-second window. ml-connector tracks token usage and backs off when approaching the daily limit, allowing queued jobs to drain before resuming. It also respects burst limits and retries with exponential backoff when a 429 response is received.