This documentation describes the old version of our handlebars powered mapper which is not available by default. We will stop supporting it by the end of Q1 2018. Please read the Migration guide to the new mapping language to get started with the new JSONata powered mapper.

The Data Mapper is the essential component that is included in any integration flow at the platform. However, we would like to think about it as the main bread and butter of the integration process which warrants detailed explanation in its own.

Here is the general logic behind

At the entry point, to each integration flow, one component is triggered to send a data which needs to be understood by the next component to act on the received data. In between these two components seats the Data Mapper which will map the incoming data to the specific fields where the next component expects them to receive.

For example, let us have a look at the most simple implementation of data mapper in WebHook to Email integration flow:

The scenario is the following: WebHook received as simple JSON file like this.

  "first_name": "John",
  "last_name": "Doe",
  "address": "Street1",
  "phone_number": 1234,
  "email_address": "",
  "animal": "cat",
  "last_checkup": "12/12/2014"

This simple JSON file is more like a template for incoming messages. It is recognised by our system and divided into separate fields which then are mapped into the outgoing e-mail fields like this:

In the example with WebHook to Mail flow, we simply mapped the necessary fields into the fields in the outgoing mail. Now, whenever we send a WebHook with similar content like above the e-mail fields will be filled in with appropriate values and the resulting e-mail would look like this:

More about schematics

Data Mapper is an action type component which exclusively works to Map the incoming data into the necessary fields defined at the Designer stage of flow integration.

In the simplistic way the Data Mapping can be referred by data transfer. For example if the data from the Component 1 needs to be transferred and matched with the values expected in the Component 2 then our Data Mapper will simply do that for your after you match the respected fields in both components. The picture below shows this in a graphical way:

Match the fields in advance: The Data Mapper can not automatically guess what values from one component to match with the next component. This needs to be set in the Designer step of your integration flow before the data can be transferred.

This is a simple example to show how the Data Mapper is used, but it works for more complex cases as seamlessly as in the current case. The Data Mapper component handles multi-nested arrays with the same fines as the simple flat arrays.