Pipedrive Connector

Connector status: Live Verified. Tajo runs this connector today.

Illustration · sample data

Sync example

Review one record

Source

Pipedrive

Connector status: Live

Destination

Your other tool

Connector status: Custom tool

Source fieldDestination fieldSample value
record.id source_id record_1042
record.updated_at updated_at 2026-10-18T08:00:00Z
record.value value sample_value
  1. Draft
  2. Review one record
  3. 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

CRM & Customer Success
PipedriveAPI / MCP / docsTajo connectorauth, mapping, syncretries, logs, checksBrevo activationcontacts, events, campaignsbackfill, webhooks, validation
Pipedrive connector flow from source system to Tajo mapping and Brevo activation.

Implementation Overview

Build target

Implement a Pipedrive connector that authenticates to the vendor surface, normalizes source records in Tajo, and activates eligible data in Brevo.

Current status

Treat this as an implementation guide. Build and validate the auth, mapping, sync, and operations paths before production use.

Primary surface

developers.pipedrive.com/docs/api/v1/swagger.json

PropertyValue
Integration surfaceOpenAPI
StatusLive
CategoryCRM & Customer Success
Setup complexitymedium
Vendor documentationdevelopers.pipedrive.com/docs/api/v1
Allowed hostNot recorded
Base URLNot recorded
OpenAPI schemadevelopers.pipedrive.com/docs/api/v1/swagger.json
MCP serverNot recorded
Last researched2026-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

ResourceDirectionConflict handling
contactsbidirectionalsource_wins, loop guard none
accountsinboundn/a
opportunitiesinboundn/a
leadsinboundn/a
usersinboundn/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 fieldBrevo destinationViaNote
emailemail—
firstNameattributes.FIRSTNAME—
lastNameattributes.LASTNAME—
nameattributes.FULL_NAME—
phoneattributes.PHONE—
idattributes.PIPEDRIVE_ID—
tajo_email_marketing_consentfilter—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.

Sources

Request early access

Enter your first name and email address. We will email you a link to confirm your request for Tajo access.

AI Assistant

Hi! Ask me anything about the docs.

This page as Markdown: pipedrive.md

Loading Markdown…