Workflows & Automation
How to Merge Contacts in GoHighLevel Workflows
By Marnix Geerkens. Published 2026-04-10. Updated 2026-06-02.
The Merge Contact action in GoHighLevel workflows detects duplicate records automatically and merges the newer one into the older, preserving all historical data on the surviving contact. You choose whether to match duplicates by email address, phone number, or both. After a merge, the workflow branches so you can take different follow-up steps depending on whether a duplicate was found.
Watch it, then build it
Get the full platform free for 30 days
That walkthrough runs on GoHighLevel. Start it free through RocketLauncher and you get 30 days instead of the usual 14, the whole platform unlocked, plus our setup help and a community of thousands of builders in 47+ countries.
30 days, not 14Full platform, nothing held backFree community and setup help
We earn a referral commission if you keep GoHighLevel after the trial. It never changes your price.
Summary. GoHighLevel's Merge Contact workflow action automates deduplication without manual CRM cleanup. When a contact passes through the action, the system checks for a matching record by email, phone, or both, then merges the newer record into the older one so the history stays intact. The workflow splits into two branches, one for when a duplicate is found and one for when it is not, giving you full control over what happens next in each case.
Related tutorials
Watch it, then build it
Get the full platform free for 30 days
30 days, not 14Full platform, nothing held backFree community and setup help
Frequently asked questions
Which contact record is kept after a merge?
The older record is always kept as the primary surviving contact.
Can goals tied to the old contact still trigger after a merge?
Goals tied to the old contact ID may not fire correctly after the merge.
Should I test this action before going live?
Yes, always test in a non-production scenario before activating on real contacts.