--- schema_version: "1" id: 451cc8edb8821f9db58ec767f5a95138ac216f34a7511295f926174bc2177809 title: Creating Inbound Message Flows collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/partner-manager/latest/create-inbound-message-flow.md canonical_url: https://docs.mulesoft.com/partner-manager/latest/create-inbound-message-flow source_site: docs.mulesoft.com content_type: documentation content_hash: b2a6501a0fabcb47f82bcfc56857501c7355a44e16ebc12b5add20eab06c48ef description: MuleSoft Documentation Site release: 2.x latest: true --- --- product: Partner Manager version: 2.x is-latest-version: true --- # Creating Inbound Message Flows > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Create inbound message flows to receive messages from partners, including messages that go through third-party connections. When you create an inbound message flow, you can validate and transform the inbound messages and then send them to your backend applications. Anypoint Partner Manager routes inbound messages based on matching identifiers configured for the partner. Before you create your first message flow, configure your [payload storage API](https://docs.mulesoft.com/partner-manager/latest/setup-payload-storage-api). To create an inbound message flow: 1. From the Partner Manager sidebar, select **Message Flows**. 2. Click **New message flow > Receive from partner**. 3. Either select an existing partner from the list or select **New** to create a new partner, as described in [Create a Partner](https://docs.mulesoft.com/partner-manager/latest/create-partner). 4. Configure the receiving endpoint. 5. Configure the source message type. 6. Select the translation map. 7. Configure the target message type. 8. Configure the target endpoint. 9. Verify that the message flow is complete. ## Configure the Receiving Endpoint The receiving endpoint (Receive from Partners endpoint) in an inbound message flow receives the messages that your partners send, either directly or via third-party connections. To configure a receiving endpoint, you can either select an existing endpoint owned by the host, partner, or third-party connection, or you can create a new endpoint. Partner Manager supports the AS2, FTP, HTTP, HTTPS, and SFTP formats for the receiving endpoint in an inbound message flow. To configure the receiving endpoint: 1. In the message flow, expand the **Receiving endpoint** section and click **Select**. 2. In the **Select an endpoint: Receive from ** window, do either of the following: - Select an existing Receive from Partners endpoint and click **Select**. - Click **New** to create a new Receive from Partners endpoint, as described in [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint). If you select an endpoint owned by a third-party connection, the messages go through that connection. After you select an endpoint, it is added to the message flow. If the protocol of the receiving endpoint is AS2, perform these additional steps: 1. Select the AS2 sender from the dropdown menu and then select either of the following: - The partner’s name, to enable your organization to receive the AS2 messages directly from the partner for whom the message flow is created - The name of a third-party connection, to enable your organization to receive the partner’s AS2 messages via a third-party connection, such as a VAN or 3PL The AS2 identifier and certificate of the selected third-party connection are used for validating the AS2 messages. 2. If there is no valid certificate in the associated profile, import one from the partner or from the third-party connection sending the AS2 message. ## Configure the Source Message Type The source message type (Receive from Partners message type) in an inbound message flow defines the structure of the messages that Partner Manager receives from a partner or third-party connection. Partner Manager supports the CSV, EDIFACT, JSON, X12, and XML formats for source message types in an inbound message flow. To configure the source message type: 1. In the message flow, expand the **Source message** section and click **Select**. 2. In the **Select message type** window, do either of the following: - Select an existing Receive from Partners message type and click **Select**. - Click **New** to create a new Receive from Partners message type, as described in [Creating Message Types](https://docs.mulesoft.com/partner-manager/latest/partner-manager-create-message-type). The message type and its validation settings are added to the message flow. If the source message type is X12 or EDIFACT and your partner expects your organization to return functional acknowledgments, perform these additional steps: 1. In the **Acknowledgement** section, select the checkbox next to **Send 997 functional acknowledgement (X12)** or **Send CONTRL functional acknowledgement (EDIFACT)**. 2. Click **Select**. 3. In the **Select an endpoint: Send acknowledgement to ** window, do either of the following: - Select the endpoint to receive the acknowledgment messages from your partner and click **Select**. - Click **New** to create a new endpoint, as described in [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint). The acknowledgment is added to the message flow. If the source message type is: - X12, select the partner and host organization’s ISA (Interchange) identifiers from the dropdown menu. - EDIFACT, select the partner and host organization’s UNA (Interchange) identifiers from the dropdown menu. - CSV, JSON, or XML, select the partner and host organization’s reference identifiers from the dropdown menu. To route inbound messages from partners matching any of the partner or host identifiers, select **All identifiers** from the dropdown menu. For more information about the order of precedence in inbound message routing, see [Inbound Message Routing](https://docs.mulesoft.com/partner-manager/latest/inbound-message-routing). ## Select the Translation Map A translation map in an inbound message flow transforms your inbound message format to your organization’s enterprise application format. Maps are created using DataWeave and are imported to the [Maps](https://docs.mulesoft.com/partner-manager/latest/maps) page. For more information about creating maps, see [Translation Maps](https://docs.mulesoft.com/partner-manager/latest/partner-manager-maps). To select the map: 1. In the message flow, expand the **Map** section. 2. Click **Select** and select the map from the table. The map is added to the message flow. Only the mapping configurations that match your source and target message types are shown. Choosing a map configuration with a different source and target message type updates the corresponding message type in your message flow. In the map for an inbound message flow, you can access source message attributes, which makes them available in the message payload. The attributes that you can access depend on the protocol of the source endpoint. For more information, see [Accessing Source Message Attributes](https://docs.mulesoft.com/partner-manager/latest/access-source-message-attributes). ## Configure the Target Message Type The target message type (Target at Host message type) in an inbound message flow defines the structure of the messages that Partner Manager sends to the backend applications. Partner Manager supports the CSV, JSON, and XML formats for the target message type in an inbound message flow. To configure the target message type: 1. In the message flow, expand the **Target at ** section. 2. In the **Message Type** section, click **Select**. 3. In the **Select message type** window, do either of the following: - Select an existing Target at Host message type and click **Select**. - Click **New** to create a new Target at Host message type. 4. Click **Save**. ## Configure the Target Endpoint The target endpoint (Target at Host Endpoint) in an inbound message flow receives the transformed messages on the backend applications. Partner Manager supports the FTP, HTTP, HTTPS, and SFTP formats for the target endpoint in an inbound message flow. To configure the target endpoint: 1. In the message flow, expand the **Target at ** section. 2. In the **Target at ** section, expand the **Endpoint** section and click **Select**. 3. In the **Select an endpoint: Target to ** window, do either of the following: - Select an existing Target at Host endpoint and click **Select**. - Click **New** to create a new Target at Host endpoint, as described in [Creating Endpoints](https://docs.mulesoft.com/partner-manager/latest/create-endpoint). After you select an endpoint, it is added to the message flow. ## Verify That the Message Flow Is Complete Partner Manager dynamically validates the message flow configuration elements for completeness and displays a green checkmark if all of the message flow building blocks are complete. After you verify the message flow configuration, you can deploy and test the message flow. ## See Also - [Inbound Message Flows](https://docs.mulesoft.com/partner-manager/latest/inbound-message-flows) - [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) - [Accessing Source Message Attributes](https://docs.mulesoft.com/partner-manager/latest/access-source-message-attributes) - [Inbound Message Routing](https://docs.mulesoft.com/partner-manager/latest/inbound-message-routing)