> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/stackai-tools/data-and-code/json-processor.md).

# JSON Processor

Filter or reshape JSON data before passing it to another step. JMESPath is a query language for selecting fields, filtering lists, and building a smaller result.

## Transform JSON

1. Provide exactly one source: **JSON Text** or **JSON File URL**. Use valid JSON with quoted property names.
2. Enter a **JMESPath Expression** that matches the structure of the source. For a list stored in `items`, `items[].name` selects the name from each item.
3. Run the tool and inspect **Result**. Confirm whether the next step needs JSON text, an object, or a list before mapping it.

**Result:** **Result** contains the selected data serialized as JSON text.

## Behavior and troubleshooting

The source limit is 15 MiB, including direct text. A missing field can produce `null` or an empty result without an invalid-expression error. Check the field names and nesting before changing the query. This tool uses JMESPath, not jq.

## Inputs

| Field                          | Parameter    | Description                                        |
| ------------------------------ | ------------ | -------------------------------------------------- |
| JSON File URL                  | `json_file`  | Public URL to a JSON file (max 15 MiB).            |
| JSON Text                      | `json_text`  | Raw JSON text to process.                          |
| JMESPath Expression (required) | `expression` | JMESPath expression used to transform/filter JSON. |

## Outputs

| Field  | Parameter | Description                        |
| ------ | --------- | ---------------------------------- |
| Result | `result`  | The JMESPath query output as JSON. |

## Related guidance

[Data Types, Lists, Missing Values, and Empty Results](https://docs.stackai.com/technical-reference/workflow-execution/data-types-lists-missing-values-and-empty-results.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/stackai-tools/data-and-code/json-processor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
