JsonTransform NodeTypeCode: json-transform

When to Use

• Parse a raw HTTP response body: An HttpRequest node returns a raw JSON string in the body field. Before accessing individual fields, use parse to convert it to a live object that downstream nodes can navigate with dot-notation expressions.
• Stringify an object for an email or log body: A workflow assembles a complex object during processing. Use stringify to convert it to pretty-printed JSON for inclusion in a debug email, Slack notification, or execution log entry.
• Minify JSON for database storage or API request body: A large metadata object should be stored as a compact JSON string in a single database column. Use minify to remove all whitespace before the DB insert, reducing storage size.
• Extract a single deeply nested property without a full DataMapping node: An API response contains transaction.payment.processor.transactionRef. Use extract with Property: "transaction.payment.processor.transactionRef" to pull out just that value in one step.
• Merge a base object with an update overlay: A customer record from the database serves as the base. A webhook payload contains field updates. Use merge to shallow-merge the updates onto the base, producing the updated record object without writing any code.
• Remove null entries from an API response array: Some REST APIs return arrays with null placeholders for deleted items. Use filter to clean the array before passing it to a CollectionOperation or Loop node.

Configuration

Operations Reference

Output Ports

Output Fields

Sample Configurations

Parse — convert HTTP response body string to object

{
  "nodeType": "json-transform",
  "settings": {
    "Operation": "parse",
    "Source": "{{ $output.httpRequestNode.body }}"
  }
}
// transformed_data: the parsed object ready for field access

Extract — pull a single nested property

{
  "nodeType": "json-transform",
  "settings": {
    "Operation": "extract",
    "SourceOutput": "apiResponseNode",
    "Property": "data.customer.billing.address.postcode"
  }
}
// transformed_data: "EC1A 1BB" (the postcode string)

Merge — overlay webhook updates onto database record

{
  "nodeType": "json-transform",
  "settings": {
    "Operation": "merge",
    "SourceOutput": "dbFetchNode",
    "MergeWith": "{{ $output.webhookTrigger }}"
  }
}
// transformed_data: the db record with webhook fields overlaid

Minify — compact for database storage

{
  "nodeType": "json-transform",
  "settings": {
    "Operation": "minify",
    "SourceOutput": "buildMetadataNode"
  }
}
// transformed_data: "{\"key\":\"value\",\"count\":42}" (no whitespace)

Sample Output

Success Port

{
  "transformedData": {
    "orderId": "ORD-2025-00123",
    "customerName": "Acme Corporation",
    "lineItems": [
      { "sku": "PRD-001", "qty": 5, "unitPrice": 29.99, "lineTotal": 149.95 },
      { "sku": "PRD-007", "qty": 2, "unitPrice": 89.99, "lineTotal": 179.98 }
    ],
    "subtotal": 329.93,
    "tax": 26.39,
    "total": 356.32,
    "currency": "USD"
  },
  "_inputKeys": ["order_id", "customer", "items", "amounts"],
  "_outputKeys": ["orderId", "customerName", "lineItems", "subtotal", "tax", "total", "currency"]
}

Expression Reference

Node Policies & GuardRails

Pattern Examples

Pattern 1 — Parse and Extract in Sequence

An HttpRequest returns the body as a string. Parse it first, then extract the specific field needed downstream.

// HttpRequest returns: body = '{"data":{"transaction":{"id":"TXN-001","amount":5000}}}'

// Node 1: JsonTransform — parse the body string
{
  "Operation": "parse",
  "Source": "{{ $output.httpRequestNode.body }}"
}
// transformed_data = { data: { transaction: { id: "TXN-001", amount: 5000 } } }

// Node 2: JsonTransform — extract the transaction ID
{
  "Operation": "extract",
  "SourceOutput": "parseBodyNode",
  "Property": "data.transaction.id"
}
// transformed_data = "TXN-001"

Pattern 2 — Merge Customer Record with Incoming Updates

A webhook delivers partial customer updates. Fetch the full record from the DB, then merge the webhook data over it before saving.

// DB record: { id: "C-001", name: "Alice", email: "alice@old.com", tier: "standard" }
// Webhook data: { email: "alice@new.com", tier: "premium" }

// JsonTransform — merge (webhook overwrites matching fields)
{
  "Operation": "merge",
  "SourceOutput": "dbFetchCustomerNode",
  "MergeWith": "{{ $output.webhookTrigger }}"
}
// Result: { id: "C-001", name: "Alice", email: "alice@new.com", tier: "premium" }

Pattern 3 — Stringify for Debug Email

At the end of a complex processing workflow, stringify the full result object and include it in a debug notification email.

// JsonTransform — stringify the processing result
{
  "Operation": "stringify",
  "SourceOutput": "finalProcessingNode"
}

// Downstream EmailSmtp node body:
// "Processing complete. Full result:\n\n{{ $output.stringifyNode.transformed_data }}"