This page is part of the Customer.io documentation. For the complete documentation index, see llms.txt.

10

Pipedrive Destination

About this integration

Pipedrive is a CRM created for salespeople by salespeople. Our Pipedrive integration seamlessly transfers source data about leads, organizations, and deals into Pipedrive, helping you effectively manage your sales pipeline, engage with leads through personalized messages, and ultimately close more sales.

Use cases

• Sync contacts to Pipedrive automatically. Send identify calls to create or update person records in Pipedrive with names, emails, phone numbers, and custom fields—keeping your CRM current without manual entry.
• Mirror company data as organizations. Use group calls to create or update organization records in Pipedrive, so your sales team always has the latest company information.
• Create deals from product events. Fire track events when someone requests a demo or starts a trial, and map them to deals in Pipedrive with the right pipeline stage, value, and currency.
• Log activities from your app. Track events like meetings, calls, or support interactions and send them to Pipedrive as activities linked to the right person, organization, and deal.

Getting started

1. Go to Data & Integrations > Integrations and select the Pipedrive entry in the Directory tab.

2. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.

3. Configure your integration.

   1. Domain: Pipedrive domain. This is found in Pipedrive in Settings > Company settings > Company domain.

   2. API Token: Pipedrive API token. This is found in Pipedrive in Settings > Personal preferences > API > Your personal API token.

   3. External ID field for a Person in Pipedrive: This is a key by which a Person in Pipedrive will be searched. It can be either Person id or a custom field containing external id. Default value is person_id.

   4. External ID field for an Organization in Pipedrive: This is a key by which an Organization in Pipedrive will be searched. It can be either Organization id or a custom field containing external id. Default value is org_id.

   5. External ID field for a Deal in Pipedrive: This is a key by which a Deal in Pipedrive will be searched. It can be either Deal id or a custom field containing external id. Default value is deal_id.

4. Click Enable Destination.

Actions

When you’re done setting things up, you can go to the Actions tab to see how we map incoming data to your integration.

Create or update person

This action fires on identify calls by default. It creates a person in Pipedrive or updates them if they already exist.

Pipedrive matches people using the Match field and Match value pair. By default, the match value maps to $.userId and Pipedrive searches by the person’s id field. You can change the match field to use email or a custom field instead, which is useful if your user IDs don’t correspond to Pipedrive’s internal IDs.

Pass custom field values using the Custom fields object in your action mapping. Each key should be the API key of a custom field in Pipedrive (found in Personal preferences > Data fields > Person), and the value maps to a property in your incoming event.

Create or update organization

This action fires on group calls by default. It creates an organization in Pipedrive or updates it if it already exists.

Pipedrive matches organizations using the Match field and Match value pair. By default, the match value maps to $.groupId and Pipedrive searches by the organization’s id field.

Create or update a deal

This action triggers on track events with the event name Deal Upserted by default. It creates or updates deal records in Pipedrive.

Deals can link to both a person and an organization. Each association uses its own match field/value pair, so you can connect a deal to an existing person (matched by userId) and an existing organization (matched by context.groupId).

Example payload

{
    "type": "track",
    "userId": "user-123",
    "event": "Deal Upserted",
    "properties": {
        "deal_id": "deal-456",
        "title": "Acme Corp - Enterprise Plan",
        "value": 50000,
        "currency": "USD",
        "stage_id": 2
    },
    "context": {
        "groupId": "org-789"
    }
}

Create or update an activity

This action logs activities in Pipedrive. It triggers on track events with the event name Activity Upserted by default.

Activities can link to a person, an organization, and a deal. If you pass an Activity ID, Pipedrive updates the existing activity; otherwise, it creates a new one. If you omit Subject or Type, Pipedrive defaults each to “Call”.

Create or update lead

This action creates or updates lead records in Pipedrive. It triggers on identify calls by default.

Leads in Pipedrive are separate from deals; they represent potential opportunities that haven’t entered your sales pipeline yet. You can link leads to a person and an organization, and set a Title, Amount, Currency, and Expected Close Date. The action requires either a person or organization match value to associate the lead.

Create or update a note

This action creates or updates notes in Pipedrive. It triggers on track events with the event name Note Upserted by default.

Notes attach to a deal, person, lead, or organization in Pipedrive, and you must link the note to at least one of these records. The action requires a Note Content value. Use this action to log context from your app, like support conversations or onboarding milestones, directly on the relevant Pipedrive record.

Data mapping

Match fields

Every action in Pipedrive uses a Match field and Match value pair to find existing records. The match field determines which Pipedrive field to search, and the match value is the data you’re searching for.

By default, Pipedrive searches by id, the internal Pipedrive identifier. In most cases, you’ll want to change this to a more useful field like email (for people) or a custom field that stores your internal IDs.

You can configure default match fields for people, organizations, and deals in your integration settings:

• External ID field for a Person in Pipedrive—the default field for matching people (default: id)
• External ID field for an Organization in Pipedrive—the default field for matching organizations (default: id)
• External ID field for a Deal in Pipedrive—the default field for matching deals (default: id)

You can also override these defaults per action by setting the Match field directly.

Dynamic fields

Pipedrive custom fields populate dynamically in the action configuration. When you configure an action, Customer.io fetches the available fields from your Pipedrive account so you can map data directly to custom fields without looking up API keys manually.

Visibility settings

Most actions include a Visible To field that controls who can see the record in Pipedrive:

• Owner & followers (private) (1)
• Entire company (shared) (3)

If you omit this field, Pipedrive uses the default visibility for that item type.

Things to know

• Match fields default to id, which may not be what you want. Pipedrive’s internal IDs don’t match your user IDs. Change the match field to email for people or set up a custom field in Pipedrive that stores your internal identifiers.
• Both the Create or update person and Create or update lead actions fire on identify by default. If you enable both, a single identify call runs both actions. Adjust the triggers if you only want one to fire.
• Every deal needs a title. If you create a deal without a title, the action fails. Make sure your track event includes a properties.title value, or set a default in your action mapping.
• Activities, deals, and notes use specific event names by default. These actions trigger on Activity Upserted, Deal Upserted, and Note Upserted track events respectively. You can change the trigger, but make sure your source sends events matching whatever you configure.
• Custom fields must exist in Pipedrive first. If you reference a field that doesn’t exist in your Pipedrive account, the action fails. Create custom fields in Pipedrive under Personal preferences > Data fields before mapping them.
• Pipedrive uses the domain in all API calls. Your domain is the subdomain of your Pipedrive account (for example, yourcompany in yourcompany.pipedrive.com). Find it in Settings > Company settings > Company domain.