Mapper component

The Mapper component is used to map source data to target data.

Used languages

At the moment, there are two different languages used to define transformation between input data and result:

  • JSONata

  • Handlebars template engine (will be deprecated).

    Please do not use Handlebars expression language.

JSONata expression language

The expression language is an essential part of the functionality of the integration platform. It is frequently required for syntactic and semantic data transformation. Mapper uses JSONata expressions to do complex data transformation. JSONata has many advantages for the use-case:

  • Native JSON support for input but also output. Every valid JSON document is, by default, a JSONata expression.

  • A set of built-in functions to perform content transformation, for example type transformation (string to number), string transformation (splitting, joining), and even higher-level functions (lambda, map, reduce).

  • Comprehensive selector mechanism allowing you to navigate nested JSON structures, arrays, predicated-based selectors

  • Ability to add custom functions, for example date parsing or output functions.

Visit the JSONata website for more information.

How expressions work

The following rules are defined to apply JSONata expressions to the integration platform context generically:

  • Expression is applied to each incoming message one by one. Possible runtime errors during the evaluation will be reported as errors to the platform. One input message provides one message at the output of the component.

  • Root context is the message body. It contains actual data from the previous step and, possibly, passthrough data.


This component has no trigger functions. This means it will not be accessible to select as a first component during the integration flow design.


  • Mapper

  • Jsonata mapper

© 2015- Squiz Pty Ltd