Pipedrive

Pipedrive

Send event data to Pipedrive

The configuration process for this destination mirrors Segment's setup. We've automatically modified the documentation from third-party sources to show you how to set up this destination with PostHog.

The Actions Pipedrive destination allows customers to share PostHog event data with Pipedrive. PostHog events sent to Pipedrive will either create new Entities or update existing Entities in Pipedrive.

Installation

  1. Sign in to your PostHog Workspace
  2. Click to the Data pipelines tab.
  3. Click on the Destinations tab.
  4. Use the search field to find the 'Pipedrive' destination. Click on the Actions Pipedrive tile.
  5. Click Add Destination.
  6. Select a source to connect to and click the Next button.
  7. Provide a name for your Pipedrive destination and click the Create Destination button.
  8. On the Settings tab, provide values in the Domain and API Token settings fields, then click the Save Changes button.
  9. Navigate to the Mappings tab to configure how PostHog events will be mapped to Pipedrive Entities. By default, mappings to upsert to Pipedrive's Person, Organization and Activity Entities will already be enabled. You can configure new Mappings by clicking on the New Mapping button.
  10. After you've configured and enabled your Mappings, click back to the Settings tab and enable the integration using the Enable Destination toggle. PostHog should now start sending event data to Pipedrive.

Configuration

OptionDescription
Domain
Type: string
Required: True

Pipedrive domain. This is found in Pipedrive in Settings > Company settings > Company domain.

API Token
Type: string
Required: True

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

External ID field for a Person in Pipedrive
Type: string
Required: False

This is a key by which a Person in Pipedrive will be searched. It can be either Person id or has of a custom field containing external id. Default value is person_id.

External ID field for an Organization in Pipedrive
Type: string
Required: False

This is a key by which an Organization in Pipedrive will be searched. It can be either Organization id or has of a custom field containing external id. Default value is org_id.

External ID field for a Deal in Pipedrive
Type: string
Required: False

This is a key by which a Deal in Pipedrive will be searched. It can be either Deal id or has of a custom field containing external id. Default value is deal_id.

Debug Mode
Type: boolean
Required: False

Will log configuration and request details

Using our REST API you can create this destination like so:

Terminal
# Create a new destination
curl --location 'https://us.i.posthog.com/api/environments/:project_id/hog_functions' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <POSTHOG_PERSONAL_API_KEY>' \
--data '{
"type": "destination",
"name": "Pipedrive",
"inputs": {
"domain": {
"value": ""
},
"apiToken": {
"value": ""
}
},
"enabled": true,
"template_id": "segment-actions-pipedrive"
}'

FAQ

Is the source code for this destination available?

Yes. The source code is available on GitHub.

Who maintains this?

This is maintained by Segment. If you have issues with it not functioning as intended, please let us know!

What if I have feedback on this destination?

We love feature requests and feedback. Please tell us what you think.

What if my question isn't answered above?

We love answering questions. Ask us anything via our community forum.

Parts of this page are sourced from segmentio/segment-docs under the Creative Commons Attribution 4.0 International License. The content may have been modified according to this code.