Node output parsing
Extract values from JSON produced by another workflow step.
JSON Parser component
Use JSON Parser when a previous step returns JSON and later components need specific values.
Extract values from JSON payloads and assign them to workflow variables.
What this component unlocks
The docs describe JSON Parser as a component for extracting and parsing JSON data from node output or from a URL obtained from a previous node. Builders choose the payload type, select the data source, choose the target variable, and enter the path to the specific element inside the JSON structure. The component tooltip shows the payload type, selected data source, and parsed data assigned to each variable.
Extract values from JSON produced by another workflow step.
Retrieve and parse JSON from a URL provided by a previous component.
Store extracted values in workflow variables so later components can use them cleanly.
Use cases
These examples show how this component can become part of production workflows across customer-owned systems and environments.
Use JSON Parser as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use JSON Parser as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use JSON Parser as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use JSON Parser as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use JSON Parser as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use JSON Parser as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Configuration surface
The exact fields can vary by deployment and product version, but each page gives customers a clear view of the component's intended role.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Implementation notes
Components should be easy for builders to configure and easy for operators to understand after the workflow is live.
Ensure the JSON data source is valid and accessible.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Use clear variable names.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Test with sample data to verify accurate extraction paths.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Workflow patterns
These are concept patterns that can be adapted to a customer's systems, policies, credentials, and deployment model.
Start with an event, use JSON Parser, then route the result to CRM, ticketing, or a customer-owned system.
Add validation, human approval, and logging around the component before downstream actions execute.
Deploy the component inside a customer-owned environment with credentials and logs governed by the customer.
Combine the component with packaged connectors or custom APIs when the process needs reusable system logic.
Component planning
We can scope the workflow, component configuration, credentials, deployment model, and handoff path before buildout begins.