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

Beta

Integrate HubSpot 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 HubSpot data

Account

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

Association

The Association record refers to an instance of an Association Type.

AssociationType

The Association Type object represents the relationship between two objects.

Contact

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

CustomObject

The Custom Object record refers to an instance of a Custom Object Class.

CustomObjectClass

The Custom Object Class object is used to represent a Custom Object Schema in the remote 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 HubSpot API

How does Merge interact with HubSpot’s API?

Merge interacts with HubSpot’s API through a set of pre-defined endpoints that access various types of CRM data. These interactions allow you to fetch and synchronize data from HubSpot, such as:

Contacts: Information about individual contacts, including name, email, phone number, and lifecycle stage
Companies: Company-specific details such as name, industry, size, and location
Deals: Data related to sales deals, such as deal stage, amount, close date, and associated contacts or companies
Tickets: Support-related information for tracking customer issues or requests, including ticket status and priority
Engagements: Activities such as emails, calls, tasks, notes, and meetings, which are associated with contacts, companies, or deals

Learn more about the HubSpot endpoints Merge can access.

How often does Merge sync HubSpot data?

Merge’s sync frequency depends on both your plan and the Common Models you’re using.

Daily: sync data every 24 hours
Standard: sync data either every hour or every 6 hours
High: sync data either every 3 hours or every 30 minutes
Highest: sync data either every 5 minutes or every hour

For syncing outside these intervals, you can use Merge’s Force Resync endpoint or Automatic Webhooks feature for real-time updates.

Learn more about Merge’s sync frequencies for HubSpot data.

What organizations use Merge’s HubSpot integration?

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

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

What other CRM integrations does Merge support?

In addition to HubSpot, Merge supports dozens of other CRM integrations through its CRM Unified API. Here’s a shortlist:

Salesforce
Pipedrive
Zoho CRM
Microsoft Dynamics 365
Freshsales
Copper
SugarCRM
Close
ActiveCampaign
Keap

See the full list of CRM integrations Merge supports.

How does Merge handle syncing custom data from HubSpot?

Merge can sync custom data from HubSpot through several key features:

Field Mapping: Customize how data fields from HubSpot map to your internal systems, making it easier to align data across platforms
Remote Data: Access and sync more detailed data from HubSpot without having to build complex additional integrations
Authenticated Passthrough Requests: For more advanced use cases, this feature allows you to securely pass data requests directly to HubSpot in real-time, ensuring the most up-to-date information is always available

Learn more about these features by visiting Merge’s docs.

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