DataWeave 2.0 for Absolute Beginners
If you've been following this series, you've already used DataWeave a handful of times without a full explanation — in the "Hello World" flow and in the Mule Event post. This is where we stop borrowing it and actually learn it properly. DataWeave is, without exaggeration, the single most important skill in MuleSoft development. You will write it in nearly every flow you ever build.
What DataWeave Actually Is
DataWeave is MuleSoft's built-in data transformation language — it lets you take data in one format, reshape it however you need, and output it in another format, all without reaching for external tools or writing complex custom code. Every time data needs to change shape — JSON to XML, a flat list into a nested structure, renaming fields, filtering out unwanted entries — DataWeave is the tool for the job.
One honest thing worth knowing as a beginner: DataWeave is a proprietary language — scripts you write aren't portable to other integration platforms — which is exactly why deep DataWeave skill is treated as a real, valuable specialization rather than a minor detail.
The Anatomy of a DataWeave Script
Every DataWeave script follows the same basic shape:
%dw 2.0
output application/json
---
{
message: "Hello World"
}
Three parts, always in this order:
%dw 2.0— declares the DataWeave version you're using (2.0 is standard for Mule 4)output application/json(orxml,csv, etc.) — declares what format the result should be in---followed by the actual transformation — everything after the three dashes is your transformation logic
DataWeave Is a Functional Language — What That Means for You
If you've come from an object-oriented background (Java, C#, Python classes), DataWeave will feel different at first. It's a functional language, which means it separates data from behavior and doesn't use loop control statements the way you might expect — there's no for loop or while loop in the traditional sense.
The other big difference: variables in DataWeave are immutable — once you define one, you can't reassign it a new value. If you need a "new" value, you create a new variable rather than modifying the old one. This might feel restrictive at first, but it's what makes DataWeave scripts predictable and easy to debug — a given input always produces the same output, with no hidden state changing behind your back.
Referencing Your Data: payload, attributes, vars
From the last post in this series, you already know these three:
%dw 2.0
output application/json
---
{
data: payload,
requestId: attributes.headers.'x-request-id',
savedCustomer: vars.customerId
}
This is the most common opening move in any DataWeave script: pull in whatever combination of payload, attributes, and variables you need, then reshape them.
Selectors: Getting Data Out of a Structure
To pull a specific value out of an object or array, DataWeave uses selectors:
%dw 2.0
output application/json
var input = { name: "Alice", age: 30, address: { city: "Austin" } }
---
{
name: input.name,
city: input.address.city
}
The dot (.) selector works exactly the way you'd expect if you've used JSON in any other language — chain dots to go deeper into nested structures.
String Concatenation with ++
To join strings together, DataWeave uses ++:
%dw 2.0
output application/json
---
{
myString: ("hello" ++ " " ++ "World")
}
Output: { "myString": "hello World" }
Conditionals: if / else
DataWeave supports if/else as an expression (it returns a value, rather than being a control-flow statement the way it is in most languages):
%dw 2.0
output application/json
var age = 17
---
{
status: if (age >= 18) "adult" else "minor"
}
A Realistic Example
Let's put it together — reshaping an incoming customer record:
%dw 2.0
output application/json
---
{
fullName: payload.firstName ++ " " ++ payload.lastName,
isAdult: if (payload.age >= 18) true else false,
city: payload.address.city default "Unknown"
}
This takes a payload with separate firstName/lastName fields, an age, and a nested address, and reshapes it into a flatter, cleaner structure — exactly the kind of transformation you'll write constantly in real integrations.
Where to Practice
MuleSoft provides a DataWeave Playground — a web-based sandbox where you can write and test scripts without needing a full Mule project running. This is genuinely the fastest way to build muscle memory with the syntax before you're debugging it inside a live flow. Search for "DataWeave Playground" to find the current link, and get comfortable pasting in sample JSON and experimenting.
You can also use the Transform Message component in Anypoint Studio itself as a live playground — as covered in the "Hello World" post, its Preview pane shows you the output of your script in real time as you edit it.
What's Next
You now understand the core shape of a DataWeave script. Next, we're building a proper cheat sheet — the syntax patterns you'll reach for constantly, organized so you can scan it fast while you're actually building.
Next up in this series: DataWeave Syntax Cheat Sheet (with downloadable reference)
visit ebook site - https://techebooks.myinstamojo.com/
0 Comments