Run recipe (Beta) action

LIMITED ACCESS

The Run recipe (Beta) action is a limited access release. Limited access features are those that have passed the development phase and are now ready for customer use. Our goal is to gather your input to ensure their reliable release in upcoming enhancements.

During the limited access release, Workato may update its functionality or change its availability to customers without prior notice.

The Run recipe (Beta) action enables you to retrieve or modify data in a third-party application and return it to your Workflow app dynamically based on user behavior. This allows end users of your applications to complete tasks involving external systems directly within the app interface and enables instant responses to user input, dynamic updates to components, and seamless integration with external systems within Workflow apps’ low-code environment.

Recipe outline

Key features

• Dynamic UI events: Trigger actions on page load, button click, drop-down value changes, or table row selection.
• Recipe-powered responses: Connect to external systems seamlessly and run recipes in real-time based on user actions.
• Custom behaviors: Update page components, modify input values, manage transitions, show or hide elements, and update or retrieve data from external systems.

Example use cases

The Run recipe action supports a range of business process automation (BPA) and business process management (BPM) use cases, such as:

• Build a front-end application for a CRM
• Translation app
• PTO request app
• Ticketing app

How it works

Run recipe actions are triggered by a UI event in the Workflow apps portal, such as page load, button click, or drop-down value changes, or table row selection. When this event happens, the recipe runs, retrieves or modifies data in an external system and returns the data to the application.

flowchart TD subgraph M[" "] direction TB subgraph D[&nbsp Recipe &nbsp] direction LR x(Real-time<br>event trigger runs) --> xx(Retrieves or updates<br>data in external systems) xx --> xxx(Returns data to<br>component) end subgraph R[&nbsp Workflow app &nbsp] direction LR a(Recipe output<br>populates components) end end A([UI event]) --> M --> B([App page updated]) D -.-> R classDef default fill:#fff,stroke:#67eadd,stroke-width:2px; classDef WorkatoTeal fill:#67eadd,stroke:#b3e0e1,stroke-width:2px,color:#000; classDef SubgraphDash fill:#e1fffc,stroke:#f66,stroke-width:2px,color:#000,stroke-dasharray: 5 5 classDef WorkatoPink fill:#f3c1c2,stroke:#f3c1c2,stroke-width:1px; class x,xx,xxx,a,A,C WorkatoTeal class D,R SubgraphDash class B WorkatoPink

Compatible components

The following table describes Run recipe actions, trigger events, and compatible components:

Component	Trigger event	Action description
Page	Page load	Configure a recipe to retrieve information from an external system and surface it in your app when the page loads.
Button	Button click	Configure a recipe to take action in an external system and return data to your app when a button is clicked.
Single-select and multi-select drop-down components	Drop-down value change	Configure a recipe to take action in an external system and return data to your app when an option is selected from a drop-down component.
Table	Table row selection	Configure a recipe to take action in an external system and return data to your app when a table row is selected.

Limitations

Run recipe actions have the following limitations during the limited access release:

• Recipes triggered by Run recipe actions have a maximum run time of 60 seconds.
• Long-running actions are not supported in recipes.
• Runtime user connections are not supported.
• Public (anonymous) pages don’t support Run recipe actions.

Additionally, the builder user interface (UI) is not optimized for non-workflow request scenarios. This means the UI is geared towards workflow requests and may contain language that does not apply to Run recipe actions. However, this doesn’t affect your apps' end-users.