What is the Integration Builder?

The Integration Builder is an integration platform that allows you to build and run integration workflows connecting Mitti to other business systems.

With an extensive connector library, including customizable API and database connection tools, the Integration Builder makes it possible to integrate with virtually any cloud or on-premise system.

An example of using the Integration Builder.

The Integration Builder is powered by Workato (opens in new tab), but embedded within and fully supported by Mitti. Each workflow you build is called a recipe. A recipe watches for something to happen in one system, then carries out a set of actions in another.

The Integration Builder is available on Premium Plan as a paid add-on. Contact your account manager to add the feature for your organization.

Task allowance

Your plan or add-on includes a set number of Integration Builder tasks each month. A task is each step a recipe completes successfully, so the number of tasks a recipe uses depends on how many steps it runs and how often it runs.

Plan

Integration Builder access

Tasks included each month

Premium Plan

Paid add-on, with a platform fee and a usage bundle

Set by the add-on tier you purchase

Enterprise Plan

Included in your subscription

50,000

Your allowance is shared across all your recipes and integrations, rather than set for each recipe. Unused tasks don't roll over to the next month.

Install or uninstall the Integration Builder

  1. Log in to the web app (opens in new tab).

  2. Click your organization name on the lower-left corner of the page and select Integrations.

  3. Select Integration Builder from the tab at the top of the page. Install the Integration Builder via the web app.

  4. C lick Install.

  5. Once installed, you can start creating recipes.

Depending on the apps that you use, the ones mentioned in this section can be interchanged with other apps supported by Workato.

Custom integration recipes

Build task-efficient recipes

Two recipes that do the same job can use very different numbers of tasks. A few design choices account for most of the difference.

Try the following best practices to optimize your usage.

  • Process records in batches. A batch trigger collects records into one trigger event, and a batch action writes them in one operation. Match a batch trigger with batch actions so a single run handles the whole set instead of one record at a time.

  • Narrow the trigger at the source using the app's own query where it supports one, or add a condition as the first step. Either way the recipe stops before it runs steps it doesn't need.

  • Match the polling interval to the use case. Most triggers poll every 5 minutes by default. A sync that only needs to be current by the start of the day can poll far less often.

  • Use a scheduled trigger for work that isn't time sensitive. One scheduled run over a set of records uses fewer tasks than a separate job for every record.

  • Declare variables in one step. A single "Create variables" action that declares several variables uses fewer tasks than one action for each.

  • Use a dedicated account for your integrations and filter out its own updates, so a recipe doesn't re-trigger on the change it just made.

Explore Workato's guidance on recipe design and task usage to build more efficient, well-structured workflows.

Frequently asked questions