Skip to content
  • There are no suggestions because the search field is empty.

What Are Field Transformers?

These advanced settings allow you to fine-tune how your Unito flows sync data between tools. Here's how.

In this article:

What are field transformers?

Field transformers are custom configurations that can be applied to individual Unito flows. These configurations define specific transformations and manipulations that take place between a source tool (where data is coming from) and the destination tool (where it's going). These transformations happen the moment Unito pulls data from that source tool. That means these transformed fields are essentially indistinguishable from regular fields, allowing your flow to do anything it could usually do — like filtering work items with those fields.

Here are a few examples of what these field transformers can do:

  • Concatenating two or more fields. For example, automatically adding an identifier or a priority level to an Asana task title.
  • Splitting one field into two. The mirror image of concatenating: break a single field into separate parts using a chosen separator. For example, a "Full Name" field that reads "Last, First" can be split into distinct first-name and last-name fields and mapped  into the destination tool.
  • Performing mathematical calculations. Compute values from times/dates as data syncs — for example, turning a “created date” and a “resolved date” into a "time to resolve" — so the destination tool doesn't have to.
  • Converting HTML to plain text. This can get around limitations around text and formatting in some tools.
  • Serializing objects. A transformer can pull individual pieces of data from a single field, put them in a specific order, and send that serialized data to a field in another tool in that order.
    • For example, one tool might separate an address into a street name, a city, and a country, in a single field while another field displays that address as a single line of information. A transformer can pick out the data from the first field, put it in the right order, and sync it to the second field as a single piece of data.
  • Mapping a number to a label ("T-shirt sizing"). Turn a numeric field into a friendlier label based on ranges you define. For example, a numeric effort or story-point score can be mapped to sizes: 1–3 becomes "S," 4–8 becomes "M," 9 and up becomes "L" — so stakeholders see a meaningful label instead of a raw number.
  • Latest of several dates (Max Datetime). Compare several dates and keep the more recent one. e.g. sync whichever is later — last-updated or last-commented.
  • Time between two dates (Duration). Calculate the elapsed time between two dates. e.g. created date → resolved date = "time to resolve".

How to set up a transformer

Field transformers can be applied to Unito flows through custom JSON configurations added to a flow's advanced settings. Here's how.

  1. Reach out to your account executive and ask for the JSON configuration your use case needs.
  2. Go to your Unito Dashboard and click the three dots on the flow you want to apply your configuration to.
  3. Click Edit.
  4. Click Advanced options.
  5. Paste your field transformer in the "Manual options" text box.

Limitations to keep in mind

While field transformers can make your flows a lot more flexible, they do have some limitations.

  • Not available with all connectors: Only some Unito integrations support transformers.
  • Only available with Enterprise plans: Other plans don't support transformers.
  • Only one-way: When a flow applies a transformer to a field, that field becomes a one-way field. You won't be able to sync data in both directions between fields when using field transformers.