JSON parser step
-
- UpdatedJan 30, 2025
- 4 minutes to read
- Yokohama
- Building applications
Identify structured data from a JSON payload without having to write a script. Map incoming JSON content to a complex object output that you can use in other steps or actions. At runtime, values from a JSON payload populate the complex object output.
To learn more about complex objects, see Complex data.
Roles and availability
Available as an Workflow Studio action step. Users with the action_designer role can create a custom action with one or more action steps.
Payload size limit
At runtime, JSON parser step supports payloads up to 10 MB. For larger payloads, create a Data Stream action. For more information on Data Stream actions, see Data Stream actions and pagination.
Fields
| Field | Description |
|---|---|
| Source | In the Source data field, select or drag a data pill
that contains the source JSON payload. For example, a REST step
Response Body data pill. At runtime, values from the data
source populate the complex object output. Under Source data and in the scripting window, enter an example payload to generate your complex object. For example, if parsing the response from a REST step that returns a list of users, enter the expected JSON object for a single user. You can create any example JSON payload with the following limitations:
|
| Structured Payload View | View your example payload as regular JSON, or toggle Structured Payload View to view the payload in a structured node tree. Select a node in the tree to copy the element's JSONPath. If you add new elements in the Target field manually, you can paste this JSONPath under an element's advanced options. |
| Generate Target | Select Generate Target to create the step's output structure from your example payload. Your output data structure appears in the Target field. Child elements for each object are automatically generated as type String. Alternatively, you can manually create your target complex object by adding elements in the Target field. |
| Target | View or edit the JSON payload's output structure. Create a structured output by clicking Generate Target, or manually add elements. Each element contains the following information in the Edit Object view:
Elements of type Object contain the Save as Template advanced option, which allows you to save your object's structure as a complex object template. You can then use this template to define the schema of an Object output for your action. For elements of type String, you can also add a max length, hint, and default value as advanced options. In the Target header, select Exit Edit Mode when you're
done making changes to your output's structure. You can then select the toggle
advanced inputs icon ( The JSONPath is the path to the element. Modify the JSONPath to change how your source data elements map to elements in your output. If manually adding elements, you can copy the JSONPath from a node in your example payload and paste it under an element's advanced options. |
) to add a nested child element.
) to view the JSON parser step example
This example tracks newly created problems from a production instance as defects in a test instance. First, create a new action named Parse Problems from Production. Add a REST step to retrieve a list of problems from the production instance. Then, add the JSON parser step to parse the REST step's Response Body and provide a complex object output that represents the Problem [problem] table's schema. Finally, create an action output of type Object named Problems from Production. Drop the root data pill from the JSON parser step into this output's value field.
Next, create a new flow named Sync New Problems, which is triggered daily at midnight. The first action in the flow is the Parse Problems from Production action. Then, add a For Each flow logic block and drop the data pill into the Item field. Within the For Each block, add an If flow logic block that checks if each problem's state is new, then creates a defect record in the test instance whose assignment group and short description is mapped to each new problem from the production instance.
