What this article covers:
- How to map fields
- The various field types
- Flow direction settings
- Special Unito fields
- Custom fields
- Mapping values
We've launched an evolution of our product, so some of the terminology and guidance in this article might be a bit out of date, and we're working hard to update it. You can learn more about our new workflow offering here, brush up on the new terminology here, and find out how to build your first workflow here.
When you set up a flow between two tools, Unito automatically matches up equivalent fields and synchronizes their data. This includes the obvious ones like titles and descriptions, but also some more subtle ones like due dates, durations, attachments, and priorities. You can review these defaults for the most common tools in the Unito integrations section of our help center.
But while defaults are great to get started, your workflow probably has some unique behavior or an extra field you absolutely want to sync up. Especially if you're using custom fields in tools like Asana, Wrike or Jira.
Here's how you can customize which fields are synchronized and how they translate between tools.
How to map fields
The first step is to determine the association between the fields of each tool. Note that we currently only support associating a field to a single other field; for example, you cannot sync the Asana due date to two fields in Jira.
Start by opening the Field mappings tab of your flow settings. You will see the default field mappings. You can both remove the default mappings and add new ones.
The list of fields available depends on the tool itself, as well as your custom fields configured inside those tools and blocks, if any.
Not all fields are made equal! Some are numbers, some are plain text, some have a set list of possible values. Unito recognizes those data types and will only let you map compatible types (string-to-string, date-to-date, number-to-number). When you create a new mapping, once you select a field in one tool, the list of fields in the second tool will only show the compatible fields.
See Mapping Values below for fields with a list of allowed values.
Flow direction settings
While Unito is a two-way integration platform, some fields can only sync in one direction. This is indicated by one of the three arrow/direction icons.
Sync Direction at the Field Level
Want to control the direction for each of your field mappings? Well you can! Find out more here.
Special Unito fields
If you're familiar with the tools you sync, you'll recognize most of the fields listed. Except for a few special fields we added:
- Title, description and comments
These are standard fields in all tools. They are automatically mapped and cannot be unmapped.
- Description Footer
This is a special block of text we add at the end of the description. It's great to list fields from another tool that don't have any direct comparison. For example to display a Jira Fix Version in Wrike, or an Asana Due Date in GitHub. Description footers are not editable so the flow is always one-way only. If you edit a footer, the change will be overwritten on the next update.
- Link to Task
This is a short message and link that points to the synchronized sister task. Great for quickly opening the synchronized task directly in the other tool.
Above is an example of a description footer where we've mapped the Link to Task, Attachments, and Due Date.
Tools like Wrike, Jira and Asana also let you create entirely new fields, such as effort, customer, opportunity size, etc. This is great to adapt these tools to your own workflows, and is even better when you want to sync across tools. Since Unito fully supports custom field synchronization, you can expose the full language and workflows of one tool into another.
Once a custom field is created in a tool, it will be listed in the field pull-down. We recommend you create custom fields with matching names and data types to keep things simple when synchronizing. If you try to sync priority with effort, you'll be in for some surprises...
A note on Jira custom fields: For Jira custom fields specifically, there are a few limitations on what we currently sync. For starters, the fields need to be single-valued. That means no array types or multi-select fields for now. Additionally, they have to be one of the following types:
- option (radio button or single select drop-down)
Beyond that, the sky really is the limit when it comes to custom fields!
Custom field support is only available for Team plans and up. Team plans cover one custom field, while Company and Enterprise plans can use any number of them. If you're on a Personal plan, and you want to add custom fields to your workflow please reach out to us and we can talk upgrades
Some fields have pre-defined sets of values. For example, a Status field can have values defined by a workflow (e.g. To Do, In Progress, In Review, Done), and a Labels field is filled from a list of specific labels (e.g. Enhancement, Bug, CEO-Wants-This, etc). Unito lets you also match up these values together, so they don't even need to be exactly the same in each tool.
Fields where you can map values will have an extra little customize icon, which expands into this:
Have a look at these articles for details on specific mappings: