# JSON Parser

Parse JSON strings and extract values by path using dot notation. Extract up to 5 different values in one node. Perfect for parsing rawMessage from Telegram or API responses. Supports nested objects and arrays. All outputs are strings.

## Plan availability

| Feature | Free | Starter | Pro | Enterprise |
| --- | --- | --- | --- | --- |
| Active workflows | 3 | 10 | 45 | Unlimited |

Allowances follow the [published Chatigram pricing page](https://chatigram.com/pricing/). Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.


## When to use this node

Parse JSON strings and extract values by path using dot notation. Extract up to 5 different values in one node. Perfect for parsing rawMessage from Telegram or API responses. Supports nested objects and arrays. All outputs are strings.

Add **JSON Parser** to a workflow branch using the node picker. Configure its fields in the inspector, then connect the next step.

## Configure the fields

| Field | What to enter |
| --- | --- |
| **JSON String** | The JSON text to parse. Example: {"user":{"id":123,"name":"Alice"},"message":"hello"} |
| **Path 1 (optional)** | Dot notation path to extract value. Examples:<br>• 'user.id' → 123<br>• 'user.name' → 'Alice'<br>• 'from.first_name' → first name<br>• 'message.text' → message text<br>• 'users[0].id' → first user's ID |
| **Path 2 (optional)** | Second path to extract (optional) |
| **Path 3 (optional)** | Third path to extract (optional) |
| **Path 4 (optional)** | Fourth path to extract (optional) |
| **Path 5 (optional)** | Fifth path to extract (optional) |

## Use the result

Choose the output from the variable picker in a later step. Output names below identify the values supplied by this node; the picker inserts the correct reference for your node instance.

| Output | Meaning / label |
| --- | --- |
| `value1` | Value 1 (from path1) |
| `value2` | Value 2 (from path2) |
| `value3` | Value 3 (from path3) |
| `value4` | Value 4 (from path4) |
| `value5` | Value 5 (from path5) |
| `isValid` | Is Valid JSON (true/false) |
| `success` | Success (true/false) |
| `error` | Error Message (if any) |

## Connect the next step

Connect the continuation shown on the canvas. Some nodes calculate their branches from the configured options. Read each branch label in the editor and connect the paths your workflow needs.

## Test it in a workflow

1. Configure this node with a small, recognizable test input or a test resource.
2. Check the variables from preceding steps and the connection selected in the inspector.
3. Save the workflow. For event-driven flows, generate the actual event; use **Run** only for a Manual workflow.
4. Open **Workflow Activity** and check the outcome before enabling wider use.

## If something goes wrong

- Check empty variables, selected resource IDs, and any fields that appeared after resource selection.
- Check the failed step in Workflow Activity before retrying. If the action may already have completed, inspect the destination first to avoid duplicates.
- Follow the [troubleshooting guide](/help/troubleshooting/) for a symptom-by-symptom checklist.

## Related guides

- [Work with variables](/workflows/variables/)
- [Understand branches and error handling](/workflows/branches/)
- [Browse all nodes](/reference/nodes/)



## Catalog coverage

This is the currently documented selection. Chatigram continues to add nodes, triggers, App Connections, and integrations. Use each page’s review date and the current application selectors to check what is available now; this catalog is not a fixed limit on future features.