Merge Unified's Pipedrive integration Merge Agent Handler's Pipedrive MCP server

Beta

Integrate Pipedrive with your product—along with any other
CRM
application

Connect your product to all the applications your customers use via Merge's Unified API to close more deals, retain customers, and expand to new markets

Get a demo

Sync Pipedrive data

Account

The Account object is used to represent a company in a CRM system.

Contact

The Contact object is used to represent an existing point of contact at a company in a CRM system.

Engagement

The Engagement object is used to represent an interaction noted in a CRM system.

EngagementType

The Engagement Type object is used to represent an interaction activity. A given Engagement typically has an Engagement Type object represented in the engagement_type field.

Lead

The Lead object is used to represent an individual who is a potential customer.

Note

The Note object is used to represent a note on another object.

Opportunity

The Opportunity object is used to represent a deal opportunity in a CRM system.

Stage

The Stage object is used to represent the stage of an opportunity.

Task

The Task object is used to represent a task, such as a to-do item.

User

The User object is used to represent a user with a login to the CRM system.

FAQ on integrating with Pipedrive API

Which Pipedrive API endpoints does Merge interact with?

Merge interacts with several Pipedrive API endpoints to access and manage various data types. Key endpoints include:

POST /v1/persons: Used to create new person records, accessing fields such as phone_number_type, phone_number, email_address_type, and email_address
POST /v1/activities: Utilized to create new activities, accessing the name field for engagement types
GET /v1/organizations/{organization_id}: Retrieves organization details, including address fields like country, city, state, and postal_code, as well as lead information such as company
GET /v1/persons/{person_id}: Fetches person details, accessing phone numbers and email addresses, along with lead information like first_name and last_name
GET /v1/activityTypes: Retrieves available activity types, accessing fields like activity_type, name, and remote_data
GET /v1/stages: Obtains pipeline stage information, including remote_id, name, and remote_data

Learn more about the endpoints Merge can access.

How frequently does Merge sync data with Pipedrive?

Merge synchronizes data from Pipedrive at intervals determined by your selected sync plan.

Daily: Syncs data every 24 hours
Standard: Syncs data every hour
High: Syncs data every 30 minutes
Highest: Syncs data every 5 minutes

For syncing outside of our normal sync intervals, you can use the Force Resync endpoint or Automatic Webhooks feature.

Learn more about Merge’s sync frequencies for Pipedrive.

What organizations use Merge’s integration with Pipedrive?

A wide range of companies use it, including Rilla, Telescope, Avenue, and Causal.

Learn more about how companies use Merge’s Pipedrive integration—along with other CRM integrations—here.

What CRM integrations does Merge support beyond Pipedrive?

Merge supports 20+ CRM integrations. These include:

HubSpot CRM
Salesforce
Zoho CRM
Microsoft Dynamics 365 Sales
Close
Copper
Keap
Affinity
Salesflare
Capsule CRM
Zendesk Sell

These integrations are powered by Merge's CRM Unified API, which allows developers to build once and access all supported CRMs.

See the complete list of CRM integrations Merge supports.

What are some of the benefits of using Merge’s Pipedrive integration?

Unified API: Build once and unlock integrations countless other CRM integrations, including Salesforce, HubSpot, Copper, and Zoho CRM
Cost Efficiency: Reduce engineering resources required for integration development and maintenance
Reliability: Battle-tested integrations with observability tools to monitor and troubleshoot integration performance
Increase sales: Unblock sales deals when prospects request a Pipedrive integration
Improve retention: Enable customers to realize more value from your product by adopting your Pipedrive integration

Can Merge sync custom fields from Pipedrive?

Yes, Merge supports advanced features that let you do this. These features include:

Field Mapping: Map Pipedrive’s custom fields to standardized Merge Common Models
Remote Data: Access raw Pipedrive data in its original format when required
Authenticated Passthrough Requests: Send direct API requests to Pipedrive for additional endpoints not included in the Common Models

Trusted to power integrations at

Make integrations your competitive advantage

More sales, less code, fewer headaches

Focus on your core product

Stop diverting your engineers to yet another integration and let them get back to work.

Give customer success a break

Manage your simplified integration issues in a single pane. No therapist required.

Stop losing sales due to integrations

Launch integrations in days, not quarters. Your sales team will thank you.

Seamless account linking

Integration authentication that feels like magic

Merge seamlessly manages authentication and authorization on behalf of your customers.
Offer account linking and permission controls to your users with Link for a customizable frontend or with Magic Link for URL-based authorization

View Docs

APIs made simple

The toolkit for all your integration needs

We make integrations painless with accessible API design, dead-simple SDKs, and beautiful documentation that we agonize over.

View Docs

40+ Languages

Get Employee Data

1from merge import Merge
2
3client = Merge(
4    account_token="YOUR_ACCOUNT_TOKEN",
5    api_key="YOUR_API_KEY",
6)
7client.hris.employees.list()

import { MergeClient, Merge } from '@mergeapi/merge-node-client';
const merge = new MergeClient({
  apiKey: 'YOUR_API_KEY',
  accountToken: 'YOUR_ACCOUNT_TOKEN',
});
employee = await merge.hris.employees.list()

ApiClient.instance.authentications.tokenAuth = {
  type: 'bearer',
  accessToken: 'API_KEY',
};
new EmployeesApi().employeesList('ACCOUNT_TOKEN', {}, (data) => {
  console.log(data);
});

import (
  "context"
  "fmt"
  merge "github.com/fern-api/merge-go"
  mergeclient "github.com/fern-api/merge-go/client"
  "github.com/fern-api/merge-go/hris"
)

client := mergeclient.NewClient(
  mergeclient.ClientWithAuthApiKey("<YOUR_API_KEY>"),

1ApiClient client = Configuration.getDefaultApiClient();
2client.setBasePath('https://api.merge.dev/api/ats/v1');
3ApiKeyAuth tokenAuth = client.getAuthentication('tokenAuth');
4tokenAuth.setApiKey('API_KEY');
5CandidatesApi apiInstance = new CandidatesApi(client);
6apiInstance.candidatesList('ACCOUNT_TOKEN');

import com.merge.api.MergeApiClient;
import com.merge.api.resources.hris.employees.requests.EmployeesRetrieveRequest;
import com.merge.api.resources.hris.types.Employee;
MergeApiClient mergeClient = MergeApiClient.builder()
    .accountToken("ACCOUNT_TOKEN")
    .apiKey("API_KEY")
    .build();
Employee employee = mergeClient.hris().employees().list(
    EmployeesRetrieveRequest.builder()
        .includeRemoteData(true)

> {

"id":"0958cbc6-6040-430a-848e-aafacbadf4ae","remote_id":"19202938","employee_number":"2","company":"8d9fd929-436c-4fd4-a48b-0c61f68d6178","first_name":"Dirna","last_name":"Emanuel","display_full_name":"Dirna Emanuel", "username": "dirnaemanuel", "groups": [

Meta endpoint

Programmatically access required schemas

Third-party providers require specific (and often different) fields to write data to their APIs, making your code a mess.

Dynamically fetch required data schemas from Merge’s /meta endpoint to make POST or PATCH requests that just work.

View Docs

Beyond building

Rely on the best integration observability system

Let our logs, issue detection, and automated alerts save your customer success team time, money, and headaches.

Forget maintenance - let your developers focus on building!

Start for free