One of the first things you need to do when creating a flow is picking your block of work. Here's how to pick the right one.
Table of contents:
What is a block of work?
When you create a flow, you'll be asked to connect your tools and choose a block of work. Block of work is our generic term for whatever holds your work. In some tools, that'll be a project, a board, or a repository, for example. Think of a block of work like a bucket, and your work items like marbles. A Unito flow is a bit like a bridge, letting marbles go from one bucket to another.
In most of our integrations, choosing a block of work just means picking the project you want to connect. However, some of our integrations offer the additional flexibility of not only choosing which block of work you want to connect but what kind of block as well. In other words, you get to choose which bucket you want to move marbles from.
Examples of blocks of work
Here some examples of the blocks of work you can connect with some of our most popular integrations:
-
Asana: projects
-
Jira: projects
-
GitHub: repositories
-
Trello: boards
-
HubSpot: accounts or deals
-
Salesforce: accounts
So for Asana, choosing your block of work means picking the project where your tasks live. Conversely, for HubSpot, you can choose between syncing all open tasks in your HubSpot account or drilling down to tasks related to deals.
With this extra flexibility, you can further customize your flows to your use case. For example, if you choose to use HubSpot deals as your block of work, you can build rules so your flow only syncs work items associated with HubSpot deals. If you picked the whole HubSpot account as your block of work, you'd be able to filter tasks by specific deals, but not deals as a whole.
Blocks of work and locked mappings
Field mappings are how Unito makes sure your information lands in the right place when it goes from tool to tool. Think of this a bit like translation. Each tool has its own language, and Unito makes sure that a due date in one tool is correctly interpreted as a due date by the other.
For integrations that let you choose between different blocks of works, we use specific field mappings to make your flow work properly. These are locked field mappings. Without these specific mappings, we wouldn't be able to sync information back and forth between blocks of work.
Since they're essential for syncing information from certain blocks of work, you won't be able to delete them. You'll still be able to map any other fields as usual, just not the ones involved in this mapping.
Did this answer your question?