Pipedrive Connector
Connector status: Live Verified. Tajo runs this connector today.
Illustration · sample data
Sync example
Source
Pipedrive
Connector status: Live
Destination
Your other tool
Connector status: Custom tool
Field mapping
| Source field | Destination field | Sample value |
|---|---|---|
record.id | source_id | record_1042 |
record.updated_at | updated_at | 2026-10-18T08:00:00Z |
record.value | value | sample_value |
- Draft
- Review one record
- Approve this version
Statuses describe individual connectors; they do not guarantee this sync is ready. Illustrative fields. Review the actual schema and permissions before a sync runs.
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 |
| Status | Live |
| 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
| Resource | Direction | Conflict handling |
|---|---|---|
contacts | bidirectional | source_wins, loop guard none |
accounts | inbound | n/a |
opportunities | inbound | n/a |
leads | inbound | n/a |
users | inbound | n/a |
Pipedrive is the record of the person; the one write back (upsert_contact) is matched on the email address, sets only the name and adds a phone, so a person it updates is re-read once by the next delta with the values it wrote.
Mapping To Tajo/Brevo
contacts → Brevo contact
Requires: workspace api key.
| Source field | Brevo destination | Via | Note |
|---|---|---|---|
email | email | — | |
firstName | attributes.FIRSTNAME | — | |
lastName | attributes.LASTNAME | — | |
name | attributes.FULL_NAME | — | |
phone | attributes.PHONE | — | |
id | attributes.PIPEDRIVE_ID | — | |
tajo_email_marketing_consent | filter | — | the canonical consent pair, derived from the Campaigns marketing_status; without the campaigns setting the template sends nobody |
Read for context and not projected: accounts, opportunities, leads, users.
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.