Pipedrive Connector
Connector implementation
Build the Pipedrive integration
Sales CRM for managing deals, contacts, and pipeline activities
Implementation Overview
Implement a Pipedrive connector that authenticates to the vendor surface, normalizes source records in Tajo, and activates eligible data in Brevo.
Treat this as an implementation guide. Build and validate the auth, mapping, sync, and operations paths before production use.
developers.pipedrive.com/docs/api/v1/swagger.json
| Property | Value |
|---|---|
| Integration surface | OpenAPI |
| Implementation status | Implementation required |
| Category | CRM & Customer Success |
| Setup complexity | medium |
| Vendor documentation | developers.pipedrive.com/docs/api/v1 |
| Allowed host | Not recorded |
| Base URL | Not recorded |
| OpenAPI schema | developers.pipedrive.com/docs/api/v1/swagger.json |
| MCP server | Not recorded |
| Last researched | 2026-04-12 |
Official OpenAPI YAML for v1 and v2.
Authentication
-
Use developers.pipedrive.com/docs/api/v1/swagger.json to generate or validate typed API clients and request models.
-
Keep developers.pipedrive.com/docs/api/v1 linked from the connector runbook so operators can confirm vendor behavior during incidents.
-
Store credentials per Tajo workspace and keep tenant-specific secrets out of connector configuration files.
-
Add a credential smoke test that verifies read access to a harmless resource before running backfills or enabling webhooks.
Data To Sync
Start with these inferred data domains, then confirm exact vendor resources and permissions from the source documentation:
- Contact and identity records
The connector should make source records idempotent by keeping a stable key such as a vendor object ID, email address, event ID, ticket ID, order ID, or campaign ID. If the vendor only exposes list APIs, Tajo should store the cursor strategy and replay policy explicitly.
Sync Shape
No typed contract exists for Pipedrive, so the direction of each resource and its conflict handling are not recorded. Direction is declared per resource on a connector contract; see the connector catalog for how contracts are promoted.
Mapping To Tajo/Brevo
No Brevo projection is recorded for Pipedrive. A projection is declared on a typed connector contract, and Pipedrive does not have one yet, so this page will not state a mapping it cannot source.
The conventions that apply to every connector — stable external IDs, normalization, backfill and sync strategy, error handling, and the builder checklist — are documented once under “Applies to every connector” on the connector catalog.