The JsonCut node is essential for data transformation within your workflow. It allows you to precisely extract or "cut" specific data elements from larger JSON structures before moving them to subsequent processing steps or Integrations.
How does JsonCut select the data it needs to extract?
JsonCut typically uses JSONPath expressions to navigate deeply nested JSON objects, ensuring you only retrieve the relevant fields needed for the next node in the automation pipeline.
Where should the JsonCut node be placed in an automation workflow?
It is usually placed directly after a data source node, such as one receiving data from a webhook or an application, and before any operational node that requires clean, structured input. It does not function as a workflow trigger.
Can I use the JsonCut node to filter arrays of data?
Yes, while the node focuses on extraction, powerful JSONPath expressions allow you to selectively filter items within arrays. This helps prepare large datasets coming from various Integrations before continuing the workflow.
What happens to the input data structure after it passes through the JsonCut node?
The JsonCut node outputs only the data specified by the cut operation. The output payload sent to the next node is the reduced, extracted result, making the data lighter and ready for further processing or use in another Integrations step.