DocumentationWorkflowsLogic and data
JSON node
Turns JSON strings into objects (parse) or the other way around (stringify). Handy when, say, a webhook delivers a JSON string as a field value and you want to get at the individual fields. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
7 min readUpdated
What this node does
Turns JSON strings into objects (parse) or the other way around (stringify). Handy when, say, a webhook delivers a JSON string as a field value and you want to get at the individual fields.
Use JSON as a clearly defined step in an anymize workflow.
- Processes one input.
- Provides one output for following steps.
- Runs as a regular step in the flow.
Set up the node
- 01Open a workflow and add JSON from the node catalog.
- 02Complete the required fields and map values from previous steps.
- 03Run the node with a small test record and inspect its output.
- 04Connect the successful output and activate the workflow after an end-to-end test.
Operations and modes
JSON has one focused purpose. Its available settings appear when you select the node.
Settings
| Field | Meaning | Area |
|---|---|---|
| Action | Choices: Parse (string → object), Stringify (object → string) | Standard |
| Source field | Configure this value in the node panel. | Standard |
| Target field | Configure this value in the node panel. | Standard |
| Indentation (stringify) | Configure this value in the node panel. | Standard |
Inputs and outputs
| Input | Meaning | Type |
|---|---|---|
| Standard | Receives the complete result from the previous step. | JSON |
| Output | Meaning | Type |
|---|---|---|
| Standard | Makes the result available to the next step as JSON. | JSON |
Example and test run
Test-run example: begin with a small, recognizable record. Inspect the output and only map fields that are present there.
Test-run example
{
"input": "value"
}Access and security
Before activation, review which data enters this step and what its output contains.
Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.
Troubleshooting
- No output: inspect the latest run and confirm that the previous node returned the expected fields.
- Empty variable: open the previous step output and use a field name from the real test data.