Data preparation and quality

Normalize date fields

Parse configured date text or timestamps into a UTC CRM date.

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

ISO, slash YMD, and numeric epoch inputs; date target avoids timezone day shifts.

What to customize

Configure target, dateOrder, and timezone.

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": "2026/09/13"
  }
}

Sample output

sample-output.json

{
  "outputFields": {
    "output1": "2026-09-13",
    "output2": "normalized",
    "output3": "Parsed as date in UTC."
  }
}

Returned fields

output1: normalized date
output2: normalized, missing, or invalid
output3: parse details

What changes when it runs

Reads field1 and returns normalized date; invalid or missing input is never a write instruction.

Ready to try it with your rules?

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

Use this recipe