Super Actions

Super Actions are Flows built by Locoia which are contained in Actions

Overview

Super Actions are Actions for Connectors, which can contain multiple API calls and data transformations in a single step in order to make working with complex APIs more convenient.

Super Actions themselves are Flows built by Locoia, which run the necessary steps to get the expected outcome. The final step of a Super Action Flow will be the output of the Super Action step.

Whenever you add a Super Action step to a Flow, a Flow copy of the corresponding Super Action Flow will be created in your Locoia Account with the same data retention setting and view permissions (however, Super Action Flows are not visible in the Flow Builder overview or Flow Monitoring). Once the Flow using the Super Action is deleted, the corresponding Super Action Flow will be deleted as well.

When you use a Super Action in a Flow, the Debugger displays an 'S' icon:

Additionally, in the Flow Run Step, you'll find a Super Action Details button. Clicking this will open the Debugger for the Super Action Flow.

If the Super Action Flow runs successfully, the Flow Debugger will show the following details:

• Start and End: Based on the Start and End Date of the Super Action Flow

• Response Code: N/A

• Request URL: N/A

• Input: Based on the Form Input of the Super Action

• Output: Based on the last step of the Super Action Flow

Super Action Flows and Flow Runs do not count against your account limits, however, the steps run by Super Actions do count against your Flow Run steps limit.

Adding Super Action

Adding a Super Action is a two-step process:

1. Building a Flow

2. Creating a new Action.

   1. Providing Input Data to the Super Action (optional)

1. Building a Super Action Flow

Create a new Flow, which should be run every time the corresponding Super Action is run.

It can use inputs like regular references from the UI Form Schema of the Super Actions (see Providing Input Data to the Super Action)

The final step of the Flow will be the output of the Super Action, so make sure that the output is in a proper JSON format.

Requirements

There are a few requirements for these Flows:

• Can only contain the Connector for which the Super Action will be added and

• One of the following Helpers:

  • Looper

  • Boolean

  • Dict Helper

  • Rest Client

  • Spreadsheet Helper

• The Connector Auth and Dynamic Authentication ID fields should be empty

• Name the Flow according to the following schema:

  • {{ connector_name }} - {{ action_name }} - Super Action

    For instance: Oracle NetSuite - get_customers_with_details - Super Action

2. Creating a Super Action

The Super Action is essentially a standard Action. However, you don't need to specify the method, endpoint, request body template, or request header template. Instead, the Super Action Flow needs to be linked in the Super Action Flow field.

2.1 Providing Input Data to the Super Action

If the Super Action Flow uses any references, these need to be added to the UI Form Schema, so that users can enter values for them in their Flows. To do that, specify the expected fields in the UI Form Schema within the Super Action settings:

Example of UI Form Schema for Super Action

In this case, when opening a Super Action you will see a regular input field. In Embed, you can request input from the user via Form Helper and then reference the Form Helper in the Super Action.

Updating Super Actions

Before updating a Super Action make sure that the updated Super Action Flow produces the same output as before (i.e. is backward compatible in Flows where it is used) or that the Super Action is not used in any Flows.

Then simply update the Super Action Flow and click the Sync Flow Copies button in the action itself, this will then update all existing Super Action Flow copies for all customers immediately.

Error in Super Action Flow

If an error happens in the Super Action Flow, the error details are passed to the step Super Action step:

Super Action with an error