Data preparation and quality
Normalize company names
Normalize company display names while retaining legal source text.
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
Whitespace and title casing plus configured terminal suffix formatting.
What to customize
Configure suffixes and preserveLegal.
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": " acme inc. "
}
}Sample output
sample-output.json
{
"outputFields": {
"output1": "Acme INC.",
"output2": "changed",
"output3": "Legal source preserved in input field."
}
}Returned fields
- output1
- display name
- output2
- changed, unchanged, or invalid
- output3
- transformation reason
What changes when it runs
Reads field1 and returns a normalized display value; no CRM writes.
Ready to try it with your rules?
Map your inputs, test a sample and publish the version you’ve checked.