A Alumio vivid purple arrow pointing to the right, a visual representation of how to access more page material when clicking on it.
Go back

Alumio deep dive: A basic transformer

By
Published on
May 19, 2020
Updated on
June 24, 2026
IN CONVERSATION WITH
Email icon
Email icon

Data sent from one application to another needs to be made compatible to be accepted. The exchange protocol and file types can be different (SOAP, REST), but so can the specific required information (ex. filter out unneeded information or add a new required field), the way values are described (ex. "red"/"blue"/"green" versus "R"/"B"/"G" versus 0/1/2) and other similar - but critical - details.

Alumio calls this transforming data, and the building block for that a transformer. A transformer is a reusable building block, and the parts that make up a transformer are reusable and precreated for Alumio users. It is the most powerful and flexible part of Alumio that provides non-programmers a quick start to create a reliable solution to connect applications.

Orders example

Suppose you are using Alumio to transfer orders from your e-commerce website to a Warehouse Management System (WMS), so that products can be shipped and your customer is satisfied. What you may find, when you ask your online shop for the latest orders, that it gives a list of orders paid as well as those not yet paid. Surely, the customer should pay before receiving items!

A simplified list of orders, provided by the e-commerce website:

Magement-Data-from-Online-Shop.png

When the state is "processing", then it should be provided to the WMS, otherwise it should be skipped until it is paid.

Alumio can apply a transformer to this list. Such a transformer can look like this:

Figure: transformer with explanation
Figure: transformer with explanation

Alumio contains a transformer tester to see how it behaves when provided with actual data:

Magement-Transformer-Tester.png

In the image above you can see how the second item of the list was removed and the other two items were kept. It works as expected and can be implemented in a Alumio installation of the client needing this solution.

In a follow-up post we will discuss the different kinds of transformers available in Alumio. Already shown here is filtering. Others kinds are: changing data, mapping data from one set onto another, moving nodes, copying nodes, transforming on conditions, and chaining multiple transformations together. Make sure to subscribe so you don't miss it!

Turn AI ambition into action

Portrait of Leonie Becher Merli, Business Development Manager at Alumio

Get a free assessment of your integration needs and next steps

Portrait of Leonie Becher Merli, Business Development Manager at Alumio

No items found.
Topics in this blog:
No items found.

FAQ

Integration Platform-ipaas-slider-right
What is a Transformer in Alumio and what does it do?

A Transformer in Alumio is a reusable building block that converts data from one format or structure into another as it moves between connected systems. Because different platforms represent the same data differently, a Transformer maps, filters, enriches, and reformats data so the receiving system accepts it correctly. Transformers are preconfigured and reusable, allowing non-developers to build reliable data conversions without writing code for each integration.

Integration Platform-ipaas-slider-right
Why is data transformation necessary in system integrations?

Data transformation is necessary because no two systems represent data the same way. An e-commerce platform might use color codes like red, blue, green while a WMS expects numerical values like 0, 1, 2. Without transformation, raw data passed between systems causes errors, rejected records, and process failures that require manual correction. Transformation logic is what makes data from one system acceptable to another.

Integration Platform-ipaas-slider-right
How does a basic Transformer work in Alumio?

A basic Transformer takes incoming data, applies a series of configured operations (filtering, renaming fields, converting value formats), and outputs the transformed data ready for the next step in the Route. Each operation is a reusable, precreated component, so users configure what the Transformer does rather than writing logic from scratch. The same Transformer can be reused across multiple integration flows.

Integration Platform-ipaas-slider-right
What is the difference between a Transformer and a connector in Alumio?

A connector handles communication with an external system: authentication, API calls, and reading or writing data. A Transformer handles what happens to the data in between: mapping fields, filtering records, changing formats, and enriching values. A typical Alumio Route uses both: a connector to pull data from system A, a Transformer to reshape it, and another connector to write it to system B.

Integration Platform-ipaas-slider-right
Can non-developers build and manage Transformers in Alumio?

Yes. Alumio's config-first approach means most Transformers are built through configuration rather than code, using precreated, reusable operations that cover the majority of data mapping and conversion scenarios. A Code Transformer is available for edge cases, but the goal is to keep specialist development out of routine integration work so integration teams can build and maintain Transformers without depending on a developer for every adjustment.

Integration Platform-ipaas-slider-right
What happens when transformation logic needs to change after an integration is live?

Because Transformers in Alumio are configured rather than custom-coded, updating transformation logic after go-live means adjusting configuration in the platform rather than editing and redeploying code. Changes can be tested in a sandbox environment before being applied to production, and Alumio's version control per Route means previous configurations are preserved if a rollback is needed.

Get a free assessment of your integration needs

Laptop screen displaying the Alumio iPaaS dashboard, alongside pop-up windows for generating cron expressions, selecting labels and route overview.