How to Use the JSON Parse Node in Titan Flow

The JSON Parse node converts a JSON string stored inside a single property into a structured JSON object that can be used throughout your Flow. This applies when the response contains JSON as a string value, rather than a native JSON object.

Business Background

External systems often return JSON as a single text string. This string cannot be used directly in a Flow. The JSON Parse node converts the text into a structured JSON object that can be mapped to variables and routed through Flow logic.

Titan Solution

Titan’s JSON Parse node reads a JSON string from a variable and generates a JSON tree. Each field in the tree can be assigned to a static variable. Nested JSON is processed automatically, so all levels of the structure can be used in your Flow.

How to Guide

Follow the steps below to configure the JSON Parse node.

Add the JSON Parse Node

1. Click Start +.
2. Choose JSON Parse as the node.
3. Click Next.

Configure the JSON Parse Window

1. Use the Select JSON Variable dropdown to choose the variable that contains your JSON string.
2. Paste a sample JSON payload into the editor.
3. Rename the node using the edit icon if required.
4. Click Generate to create the JSON tree.

Why the Generate button may be disabled:
The Generate button is only enabled after a JSON variable has been selected. If no variable is specified, Titan cannot build the JSON tree.

Map JSON Fields to Variables

Once the JSON tree is generated:

1. Select a field in the tree.
2. Open the Store into Variable dropdown.
3. Choose an existing static variable or select + New Variable if one is not already created.

4. If creating a new variable, type the name and confirm with the ✓ checkmark or Enter.
5. Select Update to save the mapping.

Note: 

• You can create global static variables in your project settings ahead of time. These variables will appear in the Store into variable dropdown.
• Creating a new variable in Tree View adds it to Global Static Variables and makes it available to the entire Flow.
• You only need to create a variable if one does not already exist in the project.

Mapping Rules

• Each JSON field must be stored in its own variable.
• New variables must be confirmed before assignment.
• Selecting Update is required to save the mapping.

Exit Paths

The JSON Parse node supports:

• On Success – all mapped fields were extracted
• On Partial Success – some fields were extracted
• On Fail – no fields were extracted
  

Use these exits for routing or fallback handling.

Next Steps

Your parsed fields can now be used in:

• Decision nodes
• Salesforce updates
• Additional Flow logic
• Returning values to Web projects