# Use HubSpot for a record merge identity question

Example: Two contact records use similar names and different emails. The sales team wants to merge them to reduce duplicates.

By Righthand Team · 2026-10-20

Source: https://www.righthand.ai/blog/use-hubspot-for-a-record-merge-identity-question

Keep HubSpot as the source for its records. A Righthand can use available information for the decision below.

This article is from Righthand. The example and result are illustrative. This guide has no executed integration test.

## The customer task

Two contact records use similar names and different emails. The sales team wants to merge them to reduce duplicates.

[Provider documentation](https://developers.hubspot.com/docs/api-reference/latest/crm/objects/contacts/guide). The documentation gives information about contact records with properties and associations. For contact operations, applicable scopes and property values are necessary.

## Make account access explicit

If HubSpot is available in [Connections](https://docs.righthand.ai/guides/adding-your-first-connection), connect the intended account. Give the Righthand access to that connection.

Provider documentation does not establish installed Righthand operations. Examine the connection’s available tools before assigning direct account work.

For direct account work, the connection must have the necessary read or write operation and permission. If that operation is unavailable, supply the information in a message. The owner must make any account change in that case.

[Connection Permissions](https://docs.righthand.ai/guides/add-a-connection) gives information about account access and tool permissions. Give only the access necessary for the identified task.

## The request to the Righthand

> Read the two identified records.
>
> Compare supplied identity evidence.
>
> Send uncertain identity to the CRM owner.
>
> Keep both records unchanged.
>
> Send the owner the result before 3 PM Friday.
>
> Use Pacific time.

## Use the provider records for the result

Identify the contact through an exact reference or verified email. Keep individual properties distinct from company and deal context. Review a proposed change before writing it.

A merge can combine information from different people.

For a permitted write, examine the resulting account record. A proposal does not establish a completed change.

For an external message, identify the recipient and permitted task. **Ask** uses an explicit instruction or approval. Connection tool permissions are another required control. [Communications Policy](https://docs.righthand.ai/security/external-communications).

## An illustrative result and next step

> The records have similar names but no supplied evidence that they identify one person.

The owner examines identity before giving a merge decision.

## Try one account task

1. Give the Righthand one identified source record.
2. Compare its result with that source.
3. Examine the account record after a permitted write.
4. Examine the work in [Activity](https://docs.righthand.ai/guides/working-with-your-righthand).

If a direct operation is unavailable, give the source information in a message. This does not establish a direct integration.

## When the account tools are sufficient

Use HubSpot directly when its existing view gives the complete answer and no other conversation is necessary. A person can make the decision from that view.

[Compare plans](https://www.righthand.ai/pricing). [Get a Righthand](https://teams.righthand.ai).