Covered in this article
Related pages
Flow Linking Technical Notes Flow Linking Usage Example
Latest Changelog
Version 1.1.0 ()
Flow Linking component

Flow Linking component

The component to connect Flows

General information

Environment variables

There is no need to set up any environment variables manually..

However, the component needs the next environment variables:

  • ELASTICIO_API_URI
  • ELASTICIO_API_USERNAME
  • ELASTICIO_API_KEY
  • ELASTICIO_WORKSPACE_ID

Credentials

  • Shared Secret (string, required): A value to be used to authenticate all HTTP calls.

Triggers

Receive trigger from another flow

This trigger allows you to receive and validate requests from other actions.

Note: You can use the HTTP Reply component with the Reply action as the last step of the flow to get a result of the execution.

Output Metadata

  • Body from the request (Object, required).

Actions

Trigger another flow

This action allows you to trigger another flow with a request body.

Note: There are no limits on the number of flows that trigger the same flow with the Receive trigger.

Configuration Fields

  • Lookup by id - (optional, boolean): If checked, the component will use flow Id instead of flow Name to trigger another flow.
  • Retry errors - (optional, boolean): If checked, the component will retry the request in case of errors, exceptions are HTTP codes less than 500 or equal 504.

Input Metadata

  • If Lookup by id is unchecked:
    • Flow Name to Call (String Enum, required): A single flow name from a list of flows that have the “Flow Linking Component” as the trigger within the current workspace. If the number of matching flows is not exactly 1, then an error will be thrown.
  • If Lookup by id is checked:
    • Flow Id to Call (String Enum, required): A single flow id from a list of flows that have the “Flow Linking Component” as the trigger within the current workspace.

Note: Enum is only available if the number of the flows is less than 100. Otherwise, manually specify the name or ID of the flow.

  • Data to transfer (Object, required): JSON object containing data to send into the next flow.

Output Metadata

  • Response (Object, required): Response of triggering request.

Known limitations

  • Receive trigger from another flow has a restriction on receiving a sample, you need to provide it manually. Safely ignore the following error "Shared Secret" is not valid!.
  • Flow Name to Call lists all flows that contain Flow Linking Component technical trigger name - receiveTrigger.