CRM records and relationships
Propagate a parent field to children
Propagates a parent property to associated children with override protection.
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
Reports changed, preserved and failed children.
What to customize
Set parent/child types and fields.
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": "{\"parentId\":\"d1\"}"
}
}Sample output
sample-output.json
{
"outputFields": {
"output1": "planned",
"output2": "dry_run",
"output3": "provider writes suppressed"
}
}Returned fields
- output1
- updated, partial or error
- output2
- changed count
- output3
- child outcomes
What changes when it runs
Reads parent and children and patches eligible child properties.
Ready to try it with your rules?
Map your inputs, test a sample and publish the version you’ve checked.