Use this node when received data is text containing JSON. If an HTTP response already supplies an object, you can read its properties directly without adding this step.
In the next step, use {{ nodes.parse1.parsed.email }}, adapting parse1 to the node’s technical name. The field expects a data path, rather than JSON text itself or an arbitrary JavaScript expression. An already decoded value is preserved under parsed.
Technical type : parse_json. Runtime : nodulz.
Credentials and prerequisites
This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.
See the credentials guide if a remote source or execution target requires access.
Parameters
Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.
Parameter
Type
Default
Values / limits
field
string
"body"
-
Configuration help
field Field
JavaScript expression or path: input.body.title, Object.keys(input.body.meta), nodes.http1.body.data.length.
Examples
Field: nodes.http1.body
Output: nodes.parse1.parsed
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
json
{"field":"body"}
Verification
Test the valid example, then replace raw with non-JSON text: the node should fail with Field "input.raw" is not valid JSON. Next remove raw: expect Field "input.raw" is empty. Business properties are under parsed, rather than at the output root.
Parse a JSON string into an object
Usage and specifics
Use this node when received data is text containing JSON. If an HTTP response already supplies an object, you can read its properties directly without adding this step.
With this manual payload:
{ "raw": "{\"email\":\"[email protected]\",\"amount\":120}" }Set Field to the path
input.raw, without braces. Output is:{ "parsed": { "email": "[email protected]", "amount": 120 }, "field": "input.raw" }In the next step, use
{{ nodes.parse1.parsed.email }}, adaptingparse1to the node’s technical name. The field expects a data path, rather than JSON text itself or an arbitrary JavaScript expression. An already decoded value is preserved underparsed.Technical type :
parse_json. Runtime :nodulz.Credentials and prerequisites
This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.
See the credentials guide if a remote source or execution target requires access.
Parameters
Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.
fieldstring"body"Configuration help
fieldField
Examples
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
{ "field": "body" }Verification
Test the valid example, then replace
rawwith non-JSON text: the node should fail withField "input.raw" is not valid JSON. Next removeraw: expectField "input.raw" is empty. Business properties are underparsed, rather than at the output root.See also : Expressions and data, Executions, Node catalog.