Workato Terminology

These are the building blocks of a Workato integration:

• Project - a repository for an integration’s assets, including recipes and connections. A Project can have multiple sub-folders, each one representing a sync of a particular object between Unifyr and the linked application, for example Deals and Opportunities or Partner Users.

  Suppliers don’t have permission to create new projects, or edit existing ones - this is done by your Unifyr team.

• Asset - a defined item that plays a part in an integration, for example a Connection or a Recipe. Assets can be defined once then re-used in any of your integration projects, as required.

• Connection - an asset holding authorization/authentication credentials for a connection between Workato and an app.

  Each Connection is associated with one instance of the app, such as a user account, and can be re-used across Recipes.

• Recipe - a user-created automated workflow that can span multiple app integrations, consisting of one or more Triggers and associated Actions.

  Some Recipes are based on a Parent-Child model:

  • Parent - only contains a Sync rule, which identifies and pulls all records updated since the last sync
  • Child or Children - processes the individual records

• Trigger - a way of initiating the steps in a Recipe, by listening for certain events then executing a specified Action when the event occurs.

  Triggers can be set off in apps (such as Salesforce) when a certain event happens (for example, a new contact is created), when a new line is added in a file, or on a scheduled basis.

• Actions - events such as create, update, or search in a target app or control flow statements that manage business logic - executed by a Trigger in a Recipe.
• Job -  the flow of each Trigger/Step event in a Recipe.

If you want to read more about Workato, see the Workato Platform documentation (this is an external site, so we have no responsibility for the content).