CRM records and relationships
Copy contacts between CRM portals
Maps a source contact into an authorized destination HubSpot contact model.
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
Uses stable keys and never reuses source IDs.
What to customize
Configure stable key, field mapping and conflict policy for the destination connection.
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": "{\"sourceContactId\":\"c1\"}"
}
}Sample output
sample-output.json
{
"outputFields": {
"output1": "dry_run",
"output2": "",
"output3": "destination writes suppressed"
}
}Returned fields
- output1
- created, updated, skipped or error
- output2
- destination ID
- output3
- mapping details
What changes when it runs
Reads source contact, searches destination key, then creates or updates the mapped contact.
Ready to try it with your rules?
Map your inputs, test a sample and publish the version you’ve checked.