CRM records and relationships

Link records using business rules

Links records when a configured business key has exactly one match.

Available recipeIncludes configuration, sample data and tests

Make it your own

Review the setup and limits below, then open an editable copy in Turbyn.

Use this recipe

Your selection stays with you through signup.

What it does

Ambiguous and missing matches are returned without a write.

What to customize

Set source/match object types, property and association type.

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": "{\"recordId\":\"t1\",\"matchValue\":\"a@example.com\"}"
  }
}

Sample output

sample-output.json

{
  "outputFields": {
    "output1": "planned",
    "output2": "dry_run",
    "output3": "provider writes suppressed"
  }
}

Returned fields

output1: linked, unmatched, ambiguous or error
output2: matched record ID
output3: details

What changes when it runs

Searches matching records and creates one labeled association.

Ready to try it with your rules?

Map your inputs, test a sample and publish the version you’ve checked.

Use this recipe