JSON Process
JSON Process is a legacy node that filters and reshapes JSON. It is no longer in the node picker, but saved workflows keep running. Use Extract Field instead.
The JSON Process node transforms JSON data. It moves into a path of the data, keeps the items that match filter conditions, and narrows each item to the fields you choose. JSON Process is a legacy node. It no longer appears in the node picker, but workflows that already contain one keep loading and running as before. For new workflows, use Extract Field, Filter List and the other list nodes.
What to use instead
| To do this | Use |
|---|---|
| Pull one field or a nested path out of JSON | Extract Field |
| Keep only the items that match conditions | Filter List |
| Pick items by position, at random or by name | Selector |
| Put the items in order | Sort List |
| Drop repeated items | Remove Duplicates |
How a saved JSON Process node works
A JSON Process node takes JSON, or text that contains JSON, from the node before it and sends on the processed result. When the result is a list, the nodes after it can run once per item. After a run, the settings panel previews the result, or shows the error.
The node has two modes:
| Setting | What it does |
|---|---|
| Mode | Visual, the default, builds the transformation from the fields below. Advanced uses a written expression instead. |
| Input Path | Visual mode. The dot path to the array or object to process, such as data.items. Leave it empty to use the whole input. |
| Filters | Visual mode. Conditions with a field, an operator and a value. Only the items that pass are kept. The operators are equals, not equals, contains, does not contain, starts with, ends with, greater than, less than, is empty, is not empty, matches regex and is in list. |
| Projection | Visual mode. The fields to keep in each item. Press Enter or Tab to add a field. Leave it empty to keep every field. |
| Expression | Advanced mode. The transformation, written as an expression. The default, ., returns the input unchanged. The panel's Syntax reference lists what the expression can use. |
Credits
JSON Process is free.
Tips
- Rebuild when you edit. When you change a workflow that uses JSON Process, consider replacing it with Extract Field and Filter List. Both show the fields detected in the upstream data.
- Chain Extract Field for deep data. One Extract Field with Output Type set to JSON can pass part of the data to a second Extract Field, which replaces an Input Path.
Frequently asked questions
Related
Extract Field
Filter List
Selector
Web Scrape
Last updated on
QA Check
Score a text from 0 to 1 with an AI model for content, quality, consistency or safety, and get an approved or rejected decision with a short reason.
Sub-Workflow
Put a whole workflow inside another as one node with typed inputs and outputs. Create a new one in place or reuse an existing workflow, up to 5 levels deep.