Skip to main content

Pipedrive Destination

Overview​

The Pipedrive connector provides powerful data delivery capabilities for creating persons, deals, pipelines, and products in your CRM system. You can choose from pre-configured endpoint templates for common use cases or manually configure custom endpoints for specific data requirements.

Prerequisites​

Before creating a Pipedrive destination, ensure you have:

  • A configured Pipedrive credential (see Pipedrive Authorization)
  • Understanding of Pipedrive's data structure and API endpoints
  • Appropriate permissions for the Pipedrive resources you want to create or update

For complete information about Pipedrive's API capabilities, see the official Pipedrive API documentation.

Endpoint Templates​

The following pre-configured endpoint templates are available for common Pipedrive data delivery scenarios:

  • Add a Person: Create new person records in your CRM
  • Add a Deal: Create new deal records in your sales pipeline
  • Add a Pipeline: Create new sales pipelines
  • Add a Product: Create new product records in your catalog

Add a Person​

Add a Person

Create new person records in your Pipedrive CRM. This endpoint is ideal for contact management and customer onboarding automation.

  • Person Data: Provide contact information, company associations, and custom fields
  • Contact Management: Create comprehensive customer profiles
  • Custom Fields: Include custom fields specific to your CRM configuration

This endpoint creates new person records based on the data you provide. Ensure your data matches Pipedrive's expected person schema for successful creation.

Add a Deal​

Add a Deal

Create new deal records in your Pipedrive sales pipeline. This endpoint is ideal for sales automation and deal management workflows.

  • Deal Data: Provide deal value, stage, probability, and associated contacts
  • Pipeline Integration: Assign deals to specific pipelines and stages
  • Sales Tracking: Include deal metadata and custom fields

This endpoint creates new deal records based on the data you provide. Ensure your data includes required fields such as title and pipeline ID for successful creation.

Add a Pipeline​

Add a Pipeline

Create new sales pipelines in your Pipedrive CRM. This endpoint is ideal for sales process management and pipeline configuration automation.

  • Pipeline Data: Provide pipeline name, stages, and configuration settings
  • Process Management: Define custom sales processes and workflows
  • Stage Configuration: Set up pipeline stages with probabilities and settings

This endpoint creates new pipeline records based on the data you provide. Ensure your data includes required fields such as name and stage configurations for successful creation.

Add a Product​

Add a Product

Create new product records in your Pipedrive product catalog. This endpoint is ideal for product management and catalog automation.

  • Product Data: Provide product information, pricing, and inventory details
  • Catalog Management: Maintain comprehensive product catalogs
  • Pricing Information: Include cost and selling price data

This endpoint creates new product records based on the data you provide. Ensure your data includes required fields such as name for successful creation.

Manual Configuration​

If the pre-configured templates don't meet your needs, you can manually configure custom Pipedrive API endpoints.

API Method​

Select the HTTP method for your API request:

  • POST: For creating new resources (most common for Pipedrive destinations)
  • PUT: For updating existing resources
  • PATCH: For partial updates to existing resources

Data Format​

Configure how your data will be formatted for Pipedrive API consumption:

  • JSON: Most common format for Pipedrive API (recommended)
  • Form Data: For specific Pipedrive endpoints that require form encoding

JSON Configuration:

  • Content-Type: application/json
  • Data Structure: Ensure your data matches Pipedrive's expected schema

API Endpoint URL​

Configure the complete Pipedrive API endpoint URL:

  1. Base URL: Use the Pipedrive API proxy URL: https://api-proxy.pipedrive.com
  2. API Path: Specify the Pipedrive API resource you want to create or update (e.g., persons, deals, products)
  3. Resource ID: For updates, include the specific resource ID in the URL path

Example URLs:

  • https://api-proxy.pipedrive.com/persons - Create new persons
  • https://api-proxy.pipedrive.com/deals - Create new deals
  • https://api-proxy.pipedrive.com/products - Create new products

Request Headers​

Configure additional HTTP headers for API customization:

  • Authorization: Automatically handled by Nexla using your Pipedrive credential
  • Content-Type: Usually application/json for Pipedrive API
  • Accept: Specify response format (e.g., application/json)

Example headers:

Content-Type: application/json
Accept: application/json

Exclude Attributes​

Filter out unnecessary data fields before sending to Pipedrive:

  • Field Names: Specify exact field names to exclude
  • Pattern Matching: Use wildcards for multiple fields (e.g., temp_*, debug_*)
  • Nested Fields: Use dot notation for nested field exclusion (e.g., metadata.debug)

Record Batching​

Configure how multiple records are grouped for efficient API calls:

  • Batch Size: Number of records per API call (Pipedrive typically handles single records)
  • Batch Method: How to handle multiple records (usually individual API calls)
  • Error Handling: How to handle failures in batched operations

Testing Your Configuration​

After configuring your Pipedrive destination:

  1. Test Connection: Verify that Nexla can successfully connect to Pipedrive
  2. Validate Data Format: Ensure your data matches Pipedrive's expected schema
  3. Test Record Creation: Send a test record to verify the endpoint works
  4. Check Permissions: Ensure your credential has the necessary permissions for the operations

Pipedrive has strict data validation requirements. Ensure your data matches the expected schema for the resource type you're creating or updating.

Important

Always test your Pipedrive destination with appropriate permissions. Ensure your credential has access to create or update the specific Pipedrive resources you're targeting.