Inbound Message Flows

An inbound message flow receives application messages from your partner, either directly or through a third-party connection; transforms the messages to the format used by your backend applications; and forwards the messages to those applications.

The following diagram shows the components of an inbound message flow:

Inbound message flow
Setting Description Supported Formats or Protocols

Receiving endpoint

Endpoint at which a host receives transmissions from a trading partner

  • AS2

  • FTP

  • HTTP

  • HTTPS

  • SFTP

Source message type

Message type of the received message payload

  • EDIFACT

  • JSON

  • X12

  • XML

Map

DataWeave map used to transform the source message type to the target message type

N/A

Target message type

Format into which the DataWeave map transforms received messages

  • JSON

  • XML

Target endpoint

Endpoint to which the transformed message is sent (typically, a process API)

  • FTP

  • HTTP

  • HTTPS

  • SFTP

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub