Book a demo

Merge Contacts

hubspot.merge_contacts
ActionCRM & salesconnection required

Calls the HubSpot API with the connection's credentials.

Merge one contact into another with POST /crm/v3/objects/contacts/merge. The primary contact survives and absorbs the other's activities, associations and any property it has no value for.

Ask about HubSpotAll HubSpot nodesProvider API docs ↗

Connection

Required
Yes — the node will not save without one
Auth type
Bearer token
Providers
HubSpot
Secret shape
the HubSpot private-app token, or {"token": "…"}
Resolved by
config.connection_id, else node.connection_id

Configuration

2 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
primary_contact_id
The HubSpot record id of the contact that survives the merge.
stringYes——101
contact_id_to_merge
The HubSpot record id of the contact merged into the primary one.
stringYes——202

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "contact_id_to_merge": "202",
  "primary_contact_id": "101"
}

Output

One shape.

result

FieldTypeExample
id
The record's HubSpot object id.
string—
properties
The record's properties, keyed by HubSpot property name.
object—
createdAt
When the record was created, ISO 8601 UTC.
string—
updatedAt
When the record was last modified, ISO 8601 UTC.
string—
archived
True when the record sits in the recycling bin.
boolean—
{
  "archived": false,
  "createdAt": "",
  "id": "",
  "properties": {},
  "updatedAt": ""
}

Notes

  • A merge cannot be undone from the API.

Related HubSpot nodes

Templates that use HubSpot

Solutions with HubSpot

See Merge Contacts run in a workflow.

In a technical demo we add the HubSpot connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.

Book a technical demoTalk to sales