This article explains the purpose, use cases, and operational steps for the "Record Merge Action" feature, part of the third-party HubSpot app "Custome Workflow Business v2."


The primary purpose of this workflow action is to automatically merge two existing records in HubSpot (e.g., duplicate companies) using a workflow.
While HubSpot has a standard manual merge feature, this action allows you to automate the consolidation of records as part of a specific process.
This action is executed by specifying two separate Record IDs:
This feature is useful for automating data cleansing or organizational restructuring processes.
test1 and test2) that were created via API integrations or manual entry, designating one as the primary.The video shows the process of merging a company named test2 into a company named test1, resulting in the deletion of test2.
Step 1: Check Data Before Execution
test1 (Primary/to be kept) and test2 (Source/to be deleted), exist on the company index page.Step 2: Configure the Workflow and Trigger
Step 3: Add the Custom Action
Step 4: Specify the IDs to Merge
test2).test1).Step 5: Activate and Run the Workflow
test1 (the primary company).test1 record in this "test" workflow using the "Enroll in workflow" button.Step 6: Verify the Final Result
test2 (Source) record is merged into the test1 (Primary) record.test2 record has disappeared from the list, leaving only the test1 record.
No, it is not a standard feature. While HubSpot does have a standard manual function for merging records, the automated merging within a workflow explained in this article is a custom action that becomes available by installing a third-party app called "Custome Workflow Business v2."
The record specified as the "Record ID (Source)" is the one that gets deleted. This action migrates all information and associated objects from the "Source" record to the "Primary" record, and then removes the "Source" record from the database. In the article's example, test2 is the "Source" (deleted) and test1 is the "Primary" (kept).
Yes, that is possible (though it's a different setup from the video). The video shows both IDs being entered manually (as fixed values). However, assuming the action's input fields support property tokens, you could configure it as follows: Set the workflow trigger for the record you want to merge (and delete) as the "Source." In the action settings for "Record ID (Source)," use a property token to specify the ID of the record currently enrolled in the workflow. In the "Record ID (Primary)" field, manually enter the fixed ID of the record you want to keep.
We can customize this sample to match your specific business requirements.
Book Free ConsultationPut it on Trello!Need a fix for HubSpot, CMS, or GAS? Post it on Trello.
Development Requests Here