Data preparation and quality

Clean generated record names

Remove configured anchored boilerplate from generated names idempotently.

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

Only anchored configured strings are removed.

What to customize

Configure prefixes and suffixes.

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": "Copy of Proposal (draft)"
  }
}

Sample output

sample-output.json

{
  "outputFields": {
    "output1": "Proposal",
    "output2": "changed",
    "output3": "Anchored boilerplate removed with bounded repetition."
  }
}

Returned fields

output1: clean name
output2: changed, unchanged, or invalid
output3: reason

What changes when it runs

Reads field1 and returns cleaned name; no CRM writes.

Ready to try it with your rules?

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

Use this recipe