FlowRunner
Pricing
Theme

Transform Data Block: The Power Tool for Structuring Automation Data

Automation often receives data in suboptimal formats. The Transform Data block reshapes messy, unstructured data into clean, predictable outputs.

A hand-cranked machine in muted forest green with a chaotic pile of amber paper scraps tumbling in on the left and a clean stack of dusty blue ordered sheets coming out on the right, the transformation rendered as a workshop mechanism.

FlowRunner’s Transform Data block lets you reshape messy, unstructured data into clean, predictable outputs. Automation regularly receives data in suboptimal formats: nested JSON, inconsistent text, scattered values. This block provides the mechanisms to restructure it for reliable workflows.

Core Functionality

The block operates on multiple data types:

  • Objects: Map, switch, merge, or extract values from key/value structures
  • Arrays: Find extremes, filter, flatten, or iterate through lists
  • Strings: Check for text presence, extract substrings, concatenate values
  • Dates/Times: Format, calculate offsets, normalize values
  • Logic: Execute conditional operations inline without branching

Configuration happens through the Expression Editor, where dynamic values from preceding blocks combine with static inputs.

Why Transform Instead of Pass Through

Rather than passively moving data, transformations actively shape it. This approach delivers cleaner outputs, simpler debugging via TestMonitor visualization, and downstream systems receiving appropriately formatted information.

Key Operations

Notable capabilities include JSON restructuring, multi-property mapping, string containment checks, list aggregation (finding maximums), and substring extraction by index.

Practical Applications

Real-world uses include code-to-label mapping, value aggregation, ID trimming, and keyword detection for conditional routing.

Best Practices

  • Use multiple smaller transformations rather than complex single operations
  • Apply descriptive naming conventions
  • Design outputs with subsequent consumers in mind

By Mark Piller, Founder of FlowRunner·Editorial policy

See how this would work on your stack

A 30-minute walkthrough against your actual setup, or a quick message to scope the fit. No slides, no signup.