- Recipes are user-created automated workflows in Workato that span multiple apps, consisting of a trigger and one or more actions.
- Triggers are events that initiate the execution of actions in a recipe, occurring in real-time or at scheduled intervals.
- Recipe steps, which include actions, conditional actions, list actions, and so on, are executed every time a trigger event occurs.
- Connections are authorizations for recipes to interact with apps, and a job is the entire flow of each trigger event through a recipe.
Here are the core concepts and terminology that you'd need to know to use Workato.
Recipes are automated workflows built by users that can span multiple apps, such as moving new accounts from Salesforce into Zendesk as new organizations. Each recipe comprises of a trigger and one or more actions that are carried out when a trigger event is picked up.
When recipes are started, they will run automatically in the background to look for trigger events and carry out recipe actions. When they are stopped, they will cease to look for trigger events.
However, when a recipe is started again, it will pick up all the trigger events that occurred since the recipe was stopped. In other words, stop functions like pause.
You can set recipe visibility to be public or private. When they are set to be public, any Workato member can see this recipe, and make a copy for their own use.
All recipes have a unique ID that identifies them and can be found in the recipe's URL. As can be seen below, the recipe has the recipe ID
Recipe IDs can be viewed from the URL on the recipe page
The recipe above has a trigger and an action. The trigger is New Salesforce account - this trigger will fire whenever a new account is created in Salesforce. The action Create Zendesk organization will create an organization in Zendesk each time the trigger event occurs (i.e. when a new account is created in Salesforce).
Try out the hands-on introduction on Workato's Automation Institute. Complete the course and become a certified Automation Pro. Find out more here (opens new window)
Triggers determine what event to listen to execute the actions described in a recipe.
Trigger events can be set off in apps (Salesforce or JIRA) when a certain event happens (new contact is created or existing ticket is updated), when a new line is added in a file, or according to a schedule (fires at a certain time or interval).
Depending on the available API, Workato can receive trigger events in real-time, or check for the occurrence of an event periodically by polling the app.
You can learn more about triggers and how to use them here.
# Steps and actions
Recipe steps are executed every time the trigger event occurs. Recipes are required to have at least one step. The most basic step for a recipe is an action such as an action to create an organization in Zendesk.
Workato steps can be actions, conditional actions, list actions, actions that call other recipes, try/catch, etc.
# Datatree and datapills
Video guide: Data tree, data mapping and data types
Every step, including triggers, brings data into the recipe. For example a new employee in Workday trigger would bring in employee data. This data is made available in the recipe via the datatree.
The individual data fields are called datapills. You can use the datapills in subsequent steps. You can read more about datapills here.
The following is the output datatree for the trigger New Salesforce account. This datatree contains all the variables known to us and available for use whenever a trigger event occurs.
Output datatree for New Salesforce account trigger
For example, as seen in the screenshot, whenever a new Salesforce account is created, we're able to get the following values for this particular new Salesforce account:
Account description, Account fax, Account ID, Account name, Account number, Account phone, Account rating, Account site, Account source, etc.
These values can be used in subsequent steps of the recipe by being passed into input fields, as covered next.
# Input fields and fields mapping
Triggers and actions have input fields. Input fields are how triggers and actions are designed to carry out customized workflows, and they can take in variables (datapills) or constants.
When we insert variables (datapills) or constants into input fields, that's called fields mapping. You can read more about fields mapping here.
The following is an expanded view of the Create Zendesk organization action. In this view, we can see two input fields: Name and Notes.
Input fields for the action Create Zendesk organization
# Mapping variables
The variable Account name has been mapped to the Name input field. This means that for every new Salesforce account that is created, the account name of this Salesforce account will be used as the organization name of the Zendesk organization that will be created. For example, a new Salesforce account named Sattei Winery will in turn create a Zendesk organization named Sattei Winery.
Input field with variable mapping
# Mapping constants
On the other hand, the input field Notes has a constant mapped to it - the words "Synced over from Salesforce." This means that all newly created Zendesk organizations created via Workato will always have the words "Synced over from Salesforce." in its Notes field.
Input field with constant mapping
Here's an example of the new Zendesk organization created via the above mapping:
Newly created Zendesk organization Sattei Winery
For a recipe to communicate with apps via actions and triggers, it has to be authorized to interact with apps. This authorization is referred to as a connection. Connections are not tied to a recipe - a single connection can be used by multiple recipes. You can read more about app connections here.
Salesforce and Zendesk connections from the recipe view
Each time there is a trigger event, the actions in the recipe are executed. The entire flow of each trigger event through the recipe is called a job. Jobs can be successful (when actions are executed successfully), or have errors (when an action results in an error). When an error is encountered, subsequent actions are not executed. You can read more about jobs here.
# Jobs report
The job report gives a high-level summary of the all the trigger events processed by the recipe. The entire flow of each trigger event through the recipe is called a job.
Information such as date, time processed and job IDs, can be found here. From this jobs history page, users can view more detailed information about a job by clicking on it.
You can read more about job reports here.
Jobs report page
# Job details
The job details page provides step-by-step input/output details of a single trigger event as it is processed by the recipe. This page is useful for troubleshooting recipes as users are able to view the data passed into each step and the resultant output returned after each step was executed. You can read more about job details here.
Job details page showing details of the send email action
Last updated: 6/29/2023, 6:40:28 PM