ETL - We have the extract, we have the Load as visual elements but we lack the Transform. Understandable with the age of the platform.

Relying on js to do this limits the audience of the tool. implement the transformation as js behind the scenes though as boomi and mule and jitterbit and workato have there own proprietary scripting languages which always felt limiting as ‘everyone’ knows js to a point

Transformation is really where all the bugs and work is done within these platforms so make it easier

Hi Geoff,

This is something we have on the roadmap to address soon, so would be interested in how you see it working.

For example, what level of granularity would you have this at? Different nodes for every operation, or some master ‘transform’ node? If the latter, how would you see the UI looking?

1 Like


Let’s chat about it in our meeting in an hour

It is a MASSIVE topic

BUT there are no excuses for you not to investigate and borrow from Jitterbit (two products), Mulesoft (3 Products), ̶D̶e̶l̶l̶ Boomi, Workato, Integromat, Zapier as they offer trial tiers and they have already invested millions on the decisions you have to make.

First question is who is the audience…develoeprs, low-coders, no-coders…look at mule with their 3 anypoint products anypoint studio, flow designer, orchestrator…all using the same underlying tech but presented differently…

Secondly design time testing is soooooooooooooo important. Be able to test the transformation at design time instead of running it and hitting and hoping…this keeps n8n support lean as transforming data is a huge drag on support calls, secondly introduces self learning at a different level. I cant emphases this point more.

Massive topic

1 Like

Important to remember Transformation is a misleading name…these objects can do many roles such as
Enterprise Integration Patterns - Introduction to Message Transformation
Enterprise Integration Patterns - Introduction to Message Routing