Merge Contact Workflow Action in Sparkforge

The Merge Contact workflow action deduplicates contacts automatically as they move through a Sparkforge workflow. It checks the enrolled contact against existing records using your match criteria and merges the newer record into the older one when a duplicate is found.

Why use it

• Automated deduplication during workflow runs.
• Three match modes: Email, Phone Number, or Email and Phone Number.
• Cleaner CRM data for reporting and communication history.
• Workflow continues on the surviving contact after a merge.
• Visibility through Workflow Execution Logs.

Action details

Email matches contacts that share an email address. Phone Number matches on phone. Email and Phone Number requires both to match — strictest option.

How to add it to a workflow

1. Log into your sub-account.
2. Go to Automations > Workflows.
3. Open an existing workflow or create a new one.
4. Click + Add New Trigger and pick something appropriate (Contact Created, Form Submitted, Contact Changed).
5. Add the Merge Contact action.
6. Pick a Match Criteria: Email, Phone Number, or Email and Phone Number.
7. Save the action.
8. Publish and save the workflow.

Merge behavior

1. The system searches for an existing contact matching the enrolled contact by your selected criteria.
2. If a match exists, the newer record merges into the older one. The older record survives — no historical data lost.
3. If the enrolled contact is the older record, the duplicate merges into it. If the enrolled contact is newer, it merges into the older duplicate.
4. If no duplicate is found, the action is skipped and the workflow continues on the original contact.

Limitations

• Goals tied to the old contact ID may not behave as expected.
• Wait-for-reply steps can stall if the email or SMS was sent before the merge.
• Wait-for-email-event may not resume cleanly because the awaited event still references the old contact.
• Trigger link waits can fail since tracking links are bound to the original contact and message IDs.
• If the surviving contact is already in the same workflow, the merging execution ends.
• If the surviving contact was previously in the workflow and Allow Re-entry is off, the merging execution ends.