Covered in this article
Related pages
Latest Changelog
Version 1.5.0 ()
Splitter component

Splitter component

The Splitter integration connector was designed to work together with the JSONata-powered Mapper.


The Splitter Component is a fundamental part of our platform. Its primary purpose is to split arrays into separate messages or to combine separate messages into one. The splitter handles incoming messages that contain multiple elements that might need to be handled differently. At the moment, there are two actions that allow you to process incoming data. Split action takes the incoming message body and applies the configured JSONata transformation on it. Re-assemble Messages action is the opposite of the Split action. In this document, we will introduce you to all the technical aspects of the component, describe both actions in detail and show an example of using a Splitter component.

Environment variables

Component does not have any required environment variables, but we suggest to use EIO_REQUIRED_RAM_MB in order to avoid Component run out of memory and terminated error, recommended value of allocated memory is 512 MB.

Please Note: From the platform version 20.51 we deprecated the component LOG_LEVEL environment variable. Now you can control logging level per each step of the flow.

Technical Notes

The technical notes page gives some technical details about Splitter component like changelog.


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


Click here to learn more about the iPaaS