---
schema_version: "1"
id: 4b46b55da4539419c44e1e6c9d6c647ab8e2066dad079d851775851cfa11eb85
title: Inbound Message Flows
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/partner-manager/latest/inbound-message-flows.md
canonical_url: https://docs.mulesoft.com/partner-manager/latest/inbound-message-flows
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 306740ceb4b3720d3f7a989c074c458902689b4e6fedf62bf49de2d607c10089
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
product: Partner Manager
version: 2.x
is-latest-version: true
---

# Inbound Message Flows

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

An inbound message flow does the following:

1.  Receives application messages from your partner, either directly or through a third-party
    connection

2.  Transforms the messages to the format used by your back-end applications

3.  Forwards the messages to those applications

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

![A flowchart showing an inbound message flow](/mulesoft/current/en-us/partner-manager/latest/_images/pm-inbound-message-flow.png)

<table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th>Callout</th><th>Setting</th><th>Description</th><th>Supported Formats or Protocols</th></tr></thead><tbody><tr><td><p><span><img src="https://docs.mulesoft.com/partner-manager/latest/_images/pm-annotation-1.png" alt="A circle with a number 1 inside"></span></p></td><td><p>Receiving endpoint</p></td><td><p>Endpoint at which a host receives transmissions from a partner</p></td><td><div><div><ul><li><p>AS2</p></li><li><p>FTP</p></li><li><p>HTTP</p></li><li><p>HTTPS</p></li><li><p>SFTP</p></li></ul></div></div></td></tr><tr><td><p><span><img src="https://docs.mulesoft.com/partner-manager/latest/_images/pm-annotation-2.png" alt="A circle with a number 2 inside"></span></p></td><td><p>Source message type</p></td><td><p>Message type of the received message payload</p></td><td><div><div><ul><li><p>CSV</p></li><li><p>EDIFACT</p></li><li><p>JSON</p></li><li><p>X12</p></li><li><p>XML</p></li></ul></div></div></td></tr><tr><td><p><span><img src="https://docs.mulesoft.com/partner-manager/latest/_images/pm-annotation-3.png" alt="A circle with a number 3 inside"></span></p></td><td><p>Map</p></td><td><p>DataWeave map used to transform the source message type to the target message type</p></td><td><div><div><p>N/A</p></div></div></td></tr><tr><td><p><span><img src="https://docs.mulesoft.com/partner-manager/latest/_images/pm-annotation-4.png" alt="A circle with a number 4 inside"></span></p></td><td><p>Target message type</p></td><td><p>Format into which the DataWeave map transforms received messages</p></td><td><div><div><ul><li><p>JSON</p></li><li><p>XML</p></li></ul></div></div></td></tr><tr><td><p><span><img src="https://docs.mulesoft.com/partner-manager/latest/_images/pm-annotation-5.png" alt="A circle with a number 5 inside"></span></p></td><td><p>Target endpoint</p></td><td><p>Endpoint to which the transformed message is sent (typically, a process API)</p></td><td><div><div><ul><li><p>FTP</p></li><li><p>HTTP</p></li><li><p>HTTPS</p></li><li><p>SFTP</p></li></ul></div></div></td></tr></tbody></table>

## See Also

- [Creating Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/create-inbound-message-flow)

- [Deploying and Testing Message Flows](https://docs.mulesoft.com/partner-manager/latest/deploy-message-flows)

- [Modifying Message Flow Settings](https://docs.mulesoft.com/partner-manager/latest/manage-message-flows)

- [Inbound Message Routing](https://docs.mulesoft.com/partner-manager/latest/inbound-message-routing)