JSON Transform
Parse, stringify, minify, extract, merge, and filter JSON data using six purpose-built operations.
What is JSON Transform?
The JSON Transform node provides six targeted operations for working with JSON data in workflows: converting between string and object representations, compacting JSON for storage, extracting a single property, combining two objects, and cleaning null entries from arrays. It is the specialist tool for JSON manipulation, complementing Data Mapping (field-level transforms) and CodeExecute (arbitrary logic).
Operations
| Operation | Input | Output | Description |
|---|---|---|---|
parse | JSON string | Object / Array | Deserializes a JSON string into a live workflow object. Required before you can access individual fields of a JSON string response. |
stringify | Object / Array | Pretty-printed JSON string | Serializes a workflow object to a formatted JSON string with 2-space indentation. Useful for logging, email body templating, or webhook payloads. |
minify | Object or JSON string | Compact JSON string | Produces the most compact possible JSON representation — no whitespace, no formatting. Ideal for storage and API request bodies where size matters. |
extract | Object / Array | Property value | Navigates a dot-notation path within the source and returns the value at that path. Similar to Data Mapping's source_field but for a single extraction. |
merge | Two objects | Merged object | Shallow-merges two JSON objects. Properties from merge_with overwrite matching properties in the primary source. Useful for applying defaults or overlaying updates. |
filter | Array | Array (nulls removed) | Removes all null and undefined entries from a JSON array. Useful for cleaning up API responses before passing them to downstream nodes. |
Key Capabilities
- Works with both inline source data and upstream node outputs via
source_output - Supports BizFirst expressions in the
sourcefield - The
extractoperation uses dot-notation path navigation (e.g.,transaction.amount.value) - The
mergeoperation performs a shallow merge — nested objects from the primary source are replaced, not deep-merged - Both
stringifyandminifyhandle circular reference detection gracefully
Common Use Cases
| Scenario | Operation |
|---|---|
| Parse a raw HTTP response body string before accessing fields | parse |
| Beautify JSON for inclusion in a debug log email | stringify |
| Compact a large JSON payload before storing in a database field | minify |
| Pull a single nested field from a complex response without full Data Mapping | extract |
| Combine customer base data with a recent activity overlay | merge |
| Remove null placeholder entries from an API response array | filter |