# Mapping payload data

## Introduction

If your process flow is sending source data into a target connection, you should map this data using the [map shape](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/map-shape). This is done in the [usual way](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/map-shape/working-with-field-mappings) with two points to note:

* [No source details are set](#source-endpoint)
* [Mapping rows must be added manually](#add-mapping-rules-manually)

## Source endpoint

In a typical situation, the [map shape](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/map-shape) is used to map data from a source connection to a target connection. However in this scenario, we don't have a source connection - Patchworks doesn't know what data you are sending in or what system it's coming from. 

As such, you won't select any **source** details when configuring the map shape - just leave these field blank:

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FNKqpcAjToKp64oF8bi1c%2Fmap%20inbound%20api%201.png?alt=media&#x26;token=fc371efc-2f50-49a8-a9eb-e4ea85d3a4c9" alt="" width="563"><figcaption></figcaption></figure></div>

## Add mapping rules manually

Because Patchworks has no way of knowing the structure of your incoming data, mapping rules must be added manually.

For further guidance please see our [Working with field mappings](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/map-shape/working-with-field-mappings#specifying-a-mapping-field-manually) page.