Skip to main content
Feedback

An example profile mapping to message action input/output parameters

This example shows how an Integration Request Profile maps to Input and Output Message Action parameters in Flow.

Request Profile mapping example

  • The connector has mapped simple Character, Number, DateTime, and Boolean values in the Integration Request Profile respectively to primitive string, number, date/time, and Boolean values in Flow. It has mapped the date input value to the $State/Date Created system value Step 1

  • The connector has mapped a complex Object value in the Integration Request Profile to a complex Object value in Flow, using the type that it automatically created. Step 2

  • The connector has mapped a complex Array(Repeating) value in the Integration Request Profile to a complex List value in Flow, using the type that it automatically created. Step 3

note

To learn more about values and types in Flow, refer to Understanding Values, Types, Objects, and Lists.