Pipedrive CRM — Integration Research Report

Date: 2026-03-30 Status: Research complete Researcher: Claude (API Integration Research skill)

1. Summary

Pipedrive is a sales-focused CRM with an extensive, well-documented REST API that supports full CRUD operations on all core entities. Unlike ERP/accounting systems, Pipedrive does not natively handle invoices, cost centers, chart of accounts, or approval workflows — these are sales pipeline concepts (deals, leads, persons, organizations, products, activities).

Capability Matrix

Data Object	Read (GET)	Write (POST/PUT)	Delete	Webhooks	Confidence
Deals	YES	YES (create, update)	YES	YES (create, change, delete)	Confirmed
Leads	YES	YES (create, update)	YES	YES (v2 only)	Confirmed
Persons (Contacts)	YES	YES (create, update)	YES	YES	Confirmed
Organizations	YES	YES (create, update)	YES	YES	Confirmed
Products	YES	YES (create, update)	YES	YES	Confirmed
Activities	YES	YES (create, update)	YES	YES	Confirmed
Notes	YES	YES (create, update)	YES	YES	Confirmed
Files/Attachments	YES	YES (upload, multipart)	YES	No	Confirmed
Custom Fields	YES	YES (create, update)	YES	N/A	Confirmed
Pipelines & Stages	YES	YES	YES	YES	Confirmed
Subscriptions	YES	YES (recurring, installment)	YES	No	Confirmed
Webhooks	YES	YES (create, update)	YES	N/A	Confirmed
Call Logs	YES	YES (create)	YES	No	Confirmed
Users	YES	Limited	No	YES	Confirmed
Invoices	NO native API	NO	NO	NO	N/A — delegated to QuickBooks/Xero

Key takeaway: Pipedrive has excellent read AND write API coverage for CRM/sales entities. It does not have native invoice, accounting, or approval workflow APIs — these are handled via marketplace integrations (QuickBooks, Xero).

2. API Landscape

API Versions

v1 — Current stable, full coverage of all entities
v2 — Rolling out for select endpoints (Products, Pipelines, Stages, Webhooks). Migration guide available.

Authentication

Method	Use Case
API Token	Personal integrations, simple scripts
OAuth 2.0	Public/private apps, multi-tenant integrations

Base URL

https://{COMPANYDOMAIN}.pipedrive.com/api/v1/

SDKs

Official client libraries for: Node.js, PHP, Python, .NET, Ruby

Key Links

Developer Portal: https://developers.pipedrive.com/
API Reference (v1): https://developers.pipedrive.com/docs/api/v1
Developer Docs: https://pipedrive.readme.io/docs/getting-started
Postman Collection: https://www.postman.com/pipedrive-developers/pipedrive-api-collection/
Changelog: https://developers.pipedrive.com/changelog

3. Write Capability Verification

Confidence: HIGH — Pipedrive has full write (POST/PUT/PATCH/DELETE) support across all core entities.

Confirmed Write Endpoints

Entity	Create	Update	Delete	Notes
Deals	`POST /deals`	`PUT /deals/{id}`	`DELETE /deals/{id}`	Including deal products, participants, followers
Leads	`POST /leads`	`PATCH /leads/{id}`	`DELETE /leads/{id}`
Persons	`POST /persons`	`PUT /persons/{id}`	`DELETE /persons/{id}`	Multiple emails, phones, custom fields
Organizations	`POST /organizations`	`PUT /organizations/{id}`	`DELETE /organizations/{id}`
Products	`POST /products`	`PUT /products/{id}`	`DELETE /products/{id}`	v2 endpoints also available
Activities	`POST /activities`	`PUT /activities/{id}`	`DELETE /activities/{id}`
Notes	`POST /notes`	`PUT /notes/{id}`	`DELETE /notes/{id}`
Files	`POST /files` (multipart)	N/A	`DELETE /files/{id}`	Attach to deal, person, org, activity, product, lead
Custom Fields	`POST /{entity}Fields`	`PUT /{entity}Fields/{id}`	`DELETE /{entity}Fields/{id}`	16 field types incl. enum, set, monetary

Rate Limits on Writes

10,000 POST/PUT requests per 24 hours (resets midnight UTC)
Token-based rate limiting (rolled out May 2025): each request costs tokens from daily budget

4. iPaaS & Middleware Findings

Celigo

Native connector with export (read) and import (write) support
Authentication: OAuth 2.0 or token-based
Supports all standard Pipedrive entities
Can fall back to HTTP mode for unlisted endpoints
Pre-built template: Pipedrive ↔ NetSuite sync

Zapier

8,000+ integrations available
Triggers (read): New Deal, Updated Deal, New Person, Updated Person, Updated Organization, Deal/Person/Org Matching Filter
Actions (write): Create Deal, Create Person, Create Product, Update Organization, Add Product to Deal, Add Follower

Make.com

Full Pipedrive CRM module with extensive operations
Actions (write): Create Deal, Add Follower, Add Participant, Add Product to Deal, Add Subscription (recurring + installment), Cancel Subscription
Managed entities: Deals, products, persons, organizations, notes, activities, mails, followers, users, files, subscriptions, filters, pipelines, stages, leads

Summary

All major iPaaS platforms confirm full read + write capability. No hidden or undocumented endpoints discovered beyond what's in the official API docs — Pipedrive's API documentation is already comprehensive.

5. Alternative Channels

Webhooks (Outbound Push)

Event actions: create, change, delete, * (wildcard)
Event objects: activity, deal, lead, note, organization, person, pipeline, product, stage, user, *
Delivery: HTTP POST with JSON body to your endpoint
Limits: Max 40 webhooks per user; banned after 10 consecutive failures; deleted after 3 days without successful delivery
v2 webhooks available with improved reliability and lead event support

SFTP

Not available. Pipedrive does not offer SFTP-based data exchange.

Unified APIs

Pipedrive is a connector (not just customer) in several unified CRM APIs:
- Merge.dev — includes Pipedrive in CRM unified API
- Unified.to — Pipedrive CRM connector available
- These could be used as an abstraction layer if Orcha integrates with multiple CRMs

File Import (UI-based)

CSV import available via Pipedrive UI for contacts, deals, organizations
Not programmatic — not suitable for automated integration

6. Licensing & Access Requirements

Pricing Plans (as of March 2026)

Plan	Price (per seat/month, annual)	API Multiplier	Daily Token Budget (per seat)
Lite	~$14	1x	30,000 tokens
Growth	~$39	2x	60,000 tokens
Premium	~$49	5x	150,000 tokens
Ultimate	~$79	7x	210,000 tokens

Formula: 30,000 base × plan multiplier × seat count (+ purchased top-ups)

Example: 10-seat Premium plan = 1,500,000 tokens/day

What's Included in Base Plans

API access is included in ALL plans — no separate API license required
OAuth 2.0 and API token auth available on all plans
Webhooks available on all plans

Feature Gating Relevant to Integration

Feature	Required Plan
Workflow automations	Growth+
Required fields (stage gates)	Professional+
Custom fields	All plans (limits vary)
Audit logs	Ultimate only

Customer Setup Checklist

No additional purchase needed for API access
Generate API token in Settings → Personal preferences → API
For OAuth: Create app in Developer Hub (https://developers.pipedrive.com/)
Ensure adequate token budget for expected API call volume
Optional: Purchase API Token top-ups if budget insufficient

Ongoing Costs

No per-API-call charges beyond the token budget system
Token budget resets daily at midnight UTC
If budget is exhausted, requests are blocked until reset (no overage charges)

7. Orcha-Specific Deep Dive

Context

Orcha is a document processing and accounting automation platform. Pipedrive is a sales CRM. The integration use case is therefore CRM ↔ accounting bridge, not a traditional ERP integration.

Mapping Orcha Needs to Pipedrive Capabilities

Orcha Need	Pipedrive Capability	Endpoint	Confidence	Notes
Write reference data (cost centers, GL codes)	NOT APPLICABLE	N/A	N/A	Pipedrive has no accounting reference data. Custom fields could store IDs for cross-referencing.
Write transactional data (invoices, credit notes)	NOT NATIVE	N/A	N/A	Pipedrive delegates invoicing to QuickBooks/Xero. Deals + Products are the closest native concept.
Attach documents (PDF/images)	YES	`POST /files` (multipart/form-data)	High	Attach to deals, persons, orgs, activities, products, leads.
Trigger/manage approvals	PARTIAL	`PUT /deals/{id}` (move stage)	Medium	No native approval workflow. Can simulate via deal stages + required fields (Pro plan). API-triggered stage changes DO trigger automations.
Read status/lifecycle	YES	`GET /deals/{id}`, webhooks	High	Deal stage changes, won/lost status. Webhooks push real-time updates.
Sync reference data inbound	YES	`GET /organizations`, `GET /persons`, `GET /products`	High	Read customer master data, contacts, products from Pipedrive into Orcha.

Realistic Integration Scenarios

Scenario A: Pipedrive → Orcha (most likely use case)

"When a deal is won in Pipedrive, automatically create an invoice in Orcha"

Webhook on change.deal → Orcha endpoint
Filter for status = won
Read deal details + products + organization via API
Create invoice/document in Orcha with deal data
Upload generated PDF back to Pipedrive deal via POST /files

Scenario B: Orcha → Pipedrive

"When an invoice is paid in Orcha, update the deal in Pipedrive"

Orcha detects payment event
PUT /deals/{id} to update custom fields (payment status, date, amount)
Optionally move deal to "Paid" stage
Add activity note via POST /activities

Scenario C: Bidirectional Contact Sync

"Keep organizations/contacts in sync between Pipedrive and Orcha"

Webhooks for create.organization, change.organization, create.person, change.person
Periodic full sync via GET /organizations and GET /persons
Write back from Orcha: POST /organizations, PUT /persons/{id}

8. Recommended Path Forward

Architecture Recommendation: Direct API Integration

Approach	Cost	Complexity	Control	Verdict
Direct API	Free (included)	Low-Medium	Full	RECOMMENDED
iPaaS (Make/Zapier)	$$$/yr	Low	Partial	Overkill — Pipedrive API is straightforward
Unified API (Merge)	$$$/yr	Medium	Medium	Only if multi-CRM support needed later

Rationale: Pipedrive's REST API is clean, well-documented, has official SDKs, and API access is included in all plans at no extra cost. Direct integration gives full control and avoids iPaaS subscription fees.

Phased Integration Plan

Phase 1: Read & Sync (lowest risk)

Sync organizations, persons, and products from Pipedrive → Orcha
Set up webhooks for real-time change notifications
Store Pipedrive IDs as cross-references in Orcha

Phase 2: Event-Driven Document Creation

Webhook listener for deal stage changes (won deals)
Auto-create invoices/documents in Orcha from deal + product data
Upload generated PDFs back to Pipedrive deals

Phase 3: Bidirectional Status Sync

Push payment/processing status from Orcha → Pipedrive custom fields
Move deals through stages based on document lifecycle
Add activity logs for audit trail

Phase 4: Advanced (optional)

Custom field sync for accounting reference data (cost center IDs, GL codes)
Subscription management (recurring billing via Pipedrive subscriptions API)
Multi-pipeline support for different document types

Technical Implementation Notes

Auth: OAuth 2.0 for production app (recommended over API token)
Rate limiting: Monitor token consumption; Premium plan recommended for production (150k tokens/seat/day)
Webhooks: Use v2 webhooks for reliability; implement idempotency (Pipedrive may send duplicates)
Error handling: Implement exponential backoff; watch for 429 (rate limit) and webhook ban system