Convert XML to JSON or JSON to XML. Use it after an HTTP trigger or any step that produces XML or JSON text.
When to use it
- XML → JSON: Partners send SOAP or plain XML; normalize to a JSON object for
set_node, validation, or downstream HTTP APIs.
- JSON → XML: Your flow works in JSON, but an upstream system expects an XML body.
Configuration
| Field | Description |
|---|
| Operation | xml_to_json (default) or json_to_xml. |
| Unwrap SOAP Body | Only for xml_to_json. If the document looks like a SOAP envelope, use the payload inside Envelope → Body as the result. |
| Root element | Only for json_to_xml. Name of the root XML element (default root). |
| Input | Description |
|---|
data | xml_to_json: XML string (raw or expression, e.g. {{ $json['http_trigger_1'].request.body }} if the body is stored as text). json_to_xml: JSON string, or an expression that evaluates to an object or array. |
Outputs
matched_output: success or error — connect edges with source handles success / error.result: Parsed object (xml_to_json, on success).xml: XML string (json_to_xml, on success).error: Message when matched_output is error.
Notes
- XML is parsed with predictable mapping of elements and attributes to JSON (including
#text / attribute conventions from the underlying library). Very large payloads should be bounded at the gateway or proxy level.
- SOAP security headers (WS-Security), MTOM attachments, and full WSDL-driven clients are out of scope for this node; use dedicated integration or custom code if required.