A Guide To Advanced Manual Options

Unito's default features cover most use cases with just a bit of tweaking. That said, here are popular advanced options.

Table of contents:

• How to use advanced options

• translateMentions and breakMentions

• MappingFallbackMode

• onFilterOut

• earliestModifiedSince

• preferredTimezone
• Personalize each flow with your own custom JSON

How to use advanced options

Most of these advanced options involve pasting a bit of code into the Advanced features box in your Unito flow of choice.

You can find this box in just a few clicks. From the flow list, click on the upright ellipses next to the flow you want to apply an advanced option to.

From there, hit Edit in the dropdown.

This'll open your flow. Hit Advanced options.

You'll find the Advanced features box at the bottom of this screen.

Using translateMentions and breakMentions

The translateMentions manual option allows you to sync @Mentions from tool to tool. That means you could mention a user in one tool and create a link to that mapped user in the other tool.

Before you can apply this advanced option, you need to make sure that all your users are mapped correctly.

All you need to do is navigate to active users screen in the app, search for a user, and merge active users between tools. 

After your users are mapped, you can contact our product specialists to have this option enabled in your flow.

What is MappingFallbackMode?

By default, Unito automatically maps fields, lists, and sections that have the same name. For example, say you have To Do, Doing, and Done lists in two Trello boards.

Even if you only map To Do and Doing, we automatically map the Done lists. You can prevent this from happening by contacting our product specialists to have the MappingFallbackMode manual option applied to your flow.

What is onFilterOut?

When a work item is filtered out of a flow — say because it changes to an assignee not covered by your rule — we automatically archive the copy. This is to avoid clutter in your work management tools.

With onFilterOut, we can change this default setting in a few different ways:

• Closing the original work item

• Closing both work items

• Keeping work items in sync

• Doing absolutely nothing

Simply paste this JSON script into the 'Advanced Features' section of your flow:

{
  "A": {
    "options": {
      "onFilterOut": "ignore"
    }
  },
  "B": {
    "options": {
      "onFilterOut": "ignore"
    }
  }
}

What is earliestModifiedSince?

With earliestModifiedSince, you can specify a timestamp to limit the number of work items fetched by initial syncing and resyncs.

When this is implemented, your flow will only sync work items that have been created or modified after that timestamp.

Using preferredTimezone

If you want to prevent any time formatting issues from happening between tools, you can use the preferredTimezone manual option to standardize time zones across tools.

Not sure how to add this to your flow? Don't hesitate to reach out to our product specialists for help.

Personalize each flow with your own custom JSON

 Beyond the examples we've provided, you can craft your own JSON configurations to unlock even more powerful customizations.

Think outside the box:

1. Unique Filtering: Design intricate filters based on specific field values or combinations of criteria.

{
  "filter": {
    "OR": [
      { "status": { "notIn": ["Closed", "Cancelled"] } },
      { "AND": [
          { "priority": "High" },
          { "dueDate": { "before": "2024-06-01" } }
      ]}
    ]
  }
}

2. Data Manipulation: Transform data as it flows between your tools, converting formats, extracting details, or performing calculations.

{
  "transform": {
    "description": {
      "function": "function(value) { return value.replace(/\\n/g, ' '); }"
    },
    "dueDate": {
      "function": "function(value) { const daysToAdd = 7; const newDate = new Date(value); newDate.setDate(newDate.getDate() + daysToAdd); return newDate.toISOString().split('T')[0]; }"
    }
  }
}

{
  "branch": {
    "if": { "tags": { "contains": "urgent" } },
    "then": {
      "assignee": "emergency_team",
      "priority": "Highest"
    },
    "else": {
      "assignee": "default_team",
      "priority": "Medium"
    }
  }
}

Get started:

1. Brainstorm: Think about the unique challenges or specific use cases you have in your workflows.
2. Design: Sketch out the logic you want to implement using JSON's structured format.
3. Test: Experiment with your custom JSON configuration in a test flow.
4. Refine: Iterate and improve your JSON until it perfectly meets your requirements.