Home/HighLevel/Features/Workflows/How to set up the Merge Contact workflow action in HighLevel

Workflows and Automation

How to set up the Merge Contact workflow action in HighLevel

In short

The Merge Contact workflow action automatically deduplicates contacts while a workflow runs. It compares the current contact to existing records using email, phone or both, merges the newer record into the older one, and then continues the workflow on the surviving record.

AreaWorkflows · Section
Used forReal estate brokerage, Fitness studio, Ecommerce store
Setup steps8 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Founders of SaaS businesses who receive leads from multiple channels and need a single record per prospect to keep communication consistent.
  • Marketing managers at agencies that run high volume lead capture forms and want to avoid duplicate entries without manual clean up.

02Merge contact workflow actions, explained

The Merge Contact action lives inside a workflow. When the workflow reaches this step, HighLevel searches for another contact that matches the enrolled contact based on the chosen criteria, email, phone number, or both. If a matching record is found, the newer contact is merged into the older one, preserving the older record’s history. The workflow then proceeds using the surviving contact.

The action can be added to any workflow that has a trigger such as Contact Created, Form Submitted, or Contact Changed. You can give the action a custom name and select the matching rule. After saving and publishing the workflow, the merge runs automatically each time the trigger fires. Execution details appear in the Workflow Execution Logs for later review.

03How businesses use merge contact workflow action

  • Real estate brokerage. When a new lead is captured from a website form and later enters a property inquiry via phone, the workflow uses the Merge Contact action set to Email and Phone Number. The duplicate leads are merged, keeping the full interaction history for the older client record while the workflow continues sending follow up messages.
  • Fitness studio. A member signs up online and later registers at the front desk using a mobile number. The studio’s welcome workflow includes the Merge Contact action with Phone Number matching. The two records combine, ensuring class bookings and messaging reference the single surviving member profile.
  • Ecommerce store. A shopper makes a purchase on the website and later creates an account in store using the same email address. The order fulfillment workflow adds the Merge Contact action set to Email matching, merging the newer store record into the existing online profile so order history stays linked.

04How to set up and use merge contact workflow action in HighLevel

Add merge contact action

  1. Log in to your subaccount.
  2. Navigate to Automations > Workflows.
  3. Create a new workflow or open an existing one.
  4. Click the + Add New Trigger button and select a trigger that will run the merge action.
  5. Add the Contact Merged action to the workflow.
  6. In Match Criteria, select Email, Phone Number, or Email and Phone Number.
  7. Save the action.
  8. Publish and Save the workflow.

05What it looks like in HighLevel

06Settings that matter

  • Action Name. Provides a custom label for the merge step; if left blank the default name Merge Contact is used.
  • Match By *. Determines which fields are compared to find duplicate contacts, options are Email, Phone Number, or both Email and Phone Number.

07Things to know before you rely on it

  • If a goal references the old contact ID, it may not work as expected after a merge.
  • Wait for reply steps can be disrupted if the message was sent before the merge, because the workflow may still be waiting on the original context.
  • Wait for email events may not resume correctly after a merge for the same reason.
  • Trigger link waits may fail because tracking links were generated with the original contact and message IDs.
  • If the surviving contact is already in the same workflow, the merged execution ends.
  • If the surviving contact was previously in the workflow and Allow Re entry is off, the merged execution ends.

08How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Merge Contact is a smart way to keep your contact list tidy without manual effort.

If you rely on manual duplicate cleanup or have no duplicate issues, you can skip this feature.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 17, 2026

Common questions

Common questions about merge contact workflow action.

Does Merge Contact replace Contact Deduplication Preferences?

No. Deduplication preferences help prevent duplicates at entry, while Merge Contact automatically merges duplicates during workflow execution.

When should I use Merge Contact instead of the Duplicate Management & Merge Tool?

Use Merge Contact for automated handling of duplicates within a workflow. Use the Duplicate Management & Merge Tool for manual review and merging from the Contacts area.

What happens if no duplicate is found?

The action is skipped and the workflow proceeds to the next step with the original contact unchanged.

Which contact record is kept after a merge?

The older contact record remains as the surviving record, preserving its history.

Can the workflow continue after a contact is merged?

Yes. After the merge, the workflow continues on the surviving contact record.

Is there a safest match option to use?

Email and Phone Number is the strictest match and reduces unintended merges, but the best choice depends on the quality of your contact data.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.