Skip to main content
Feedback

Using Flow service component message actions with Flow

This type of Flow Service Operation maps to Message Actions in a Message step in Flow.

You can add a message step to a Flow in order to send and receive message requests between Flow and the Integration Flow Service.

A Flow uses message actions to define the interface of inputs/outputs when calling against your Flow Service Message Actions. This allows you to map values in a Flow to the inputs and outputs specified by your Flow Service.

Message actions are useful if the request/response data passed between Integration and Flow are in different formats. For example, you might pass a selected date range from a Flow into an API endpoint in order to receive back stock price data.

When you import or update an Integration connector in Flow, Flow creates actions that you can access through a Message step.

For example:

Flow Message Actions

  • You assign an Integration process named 'Retrieve' to a Flow Service component Message Action. Step 1

  • You add a 'Retrieve CRM record' Message step to the Flow canvas, and add a new Message Action to this step. Refer to Adding Message Actions to a step. Step 2

  • The Boomi Integration Service connector is selected as The connector to send the Message.

  • The available Actions in The Message to send table are then populated with the Flow Service Message Actions set up in Integration.

  • The Action can be configured by selecting the relevant value in Flow to use for each Input/Output parameter.

The Input and Output values passed to and from Message Actions are named and configured using the Request and Response profiles assigned to your Integration process.