History and lifecycle management
Merge duplicate contacts
Search contacts by a trusted key and merge only confident unprotected duplicates.
Make it your own
Review the setup and limits below, then open an editable copy in Turbyn.
Use this recipeYour selection stays with you through signup.
What it does
Protected, oversized, and low-confidence groups are review-only.
What to customize
Choose matchProperty, maxGroup, and protectedIds.
Run the included tests with your configuration and mappings. Review success, missing-input and failure results before publishing.
Expected outcome
This included example runs in dry-run mode with synthetic data. Integration tests separately cover provider responses using test doubles. It is not a live customer result.
Sample input
sample-input.json
{
"inputFields": {
"field1": "{\"matchKey\":\"a@example.com\"}"
}
}Sample output
sample-output.json
{
"outputFields": {
"output1": "planned",
"output2": "dry_run",
"output3": "No provider calls or changes were made."
}
}Returned fields
- output1
- merged, planned, review, no_match, or error
- output2
- survivor or reason
- output3
- JSON merge details
What changes when it runs
Searches contacts and issues HubSpot merge POSTs for eligible duplicates.
Ready to try it with your rules?
Map your inputs, test a sample and publish the version you’ve checked.