Pipedrive Data Source
Overview
The Pipedrive connector provides powerful data ingestion capabilities for CRM data, sales pipeline management, and customer relationship analytics. 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 data source, ensure you have:
- A configured Pipedrive credential (see Pipedrive Authorization)
- Access to the Pipedrive data you want to ingest
- Understanding of Pipedrive's data structure and API endpoints
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 ingestion scenarios:
- Get All Persons: Retrieve all person records with automatic pagination
- Get All Deals: Retrieve all deal records with automatic pagination
- Get All Pipelines: Retrieve all pipeline records with automatic pagination
- Get All Products: Retrieve all product records with automatic pagination
Get All Persons
Get All Deals
Get All Pipelines
Get All Products
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:
- GET: For retrieving data (most common for Pipedrive API)
- POST: For creating or updating resources
API Endpoint URL
Configure the complete Pipedrive API endpoint URL:
- Base URL: Use the Pipedrive API proxy URL:
https://api-proxy.pipedrive.com - API Path: Specify the Pipedrive API resource you want to access (e.g.,
persons,deals,pipelines) - Query Parameters: Add any required or optional query parameters
Example URLs:
https://api-proxy.pipedrive.com/persons- Retrieve all personshttps://api-proxy.pipedrive.com/deals- Retrieve all dealshttps://api-proxy.pipedrive.com/products- Retrieve all products
Date/Time Macros
Use dynamic datetime placeholders for flexible endpoint configuration:
${start.cron}: Current execution time in cron format${start.iso}: Current execution time in ISO 8600 format${start.unix}: Current execution time as Unix timestamp
Example with date filtering:
https://api-proxy.pipedrive.com/deals?since_timestamp=${start.unix}
Lookup-Based Macros
Reference data from other Nexla sources for dynamic endpoint configuration:
${lookup.source_name.field_name}: Access specific fields from other data sources${lookup.source_name.field_name[*]}: Access array elements from lookup sources
Path to Data
Specify which part of the Pipedrive API response contains the relevant data:
- JSON Path: Use dot notation for nested data access
$.data.items[*]- All items in the response$.data[*]- All data items in the response$.additional_data[*]- Additional data items
Metadata
Preserve contextual information from Pipedrive API responses:
$.additional_data: Pagination and metadata information$.success: API response success status$.data: Main data array containing the requested records
Request Headers
Configure additional HTTP headers for API customization:
- Authorization: Automatically handled by Nexla using your Pipedrive credential
- Content-Type: Usually
application/jsonfor Pipedrive API - Accept: Specify response format (e.g.,
application/json)
Example headers:
Content-Type: application/json
Accept: application/json
Testing Your Configuration
After configuring your Pipedrive data source:
- Test Connection: Verify that Nexla can successfully connect to Pipedrive
- Preview Data: Review a sample of the data that will be ingested
- Validate Schema: Ensure the data structure matches your expectations
- Check Rate Limits: Monitor Pipedrive's rate limiting to avoid API throttling
Pipedrive has rate limits that vary by endpoint and account type. Monitor your API usage in the Pipedrive admin panel to ensure you stay within limits.
Always test your Pipedrive data source with appropriate permissions. Ensure your credential has access to the specific Pipedrive data you're trying to retrieve.