> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/documentation/automations/actions-in-rewst/transform-actions/parse-text-to-json-transform-action.md).

# Parse text to JSON transform action

## Use case

You have received an API response of a JSON string instead of a JSON object and would like to convert it to a JSON object.

## Overview

Parse Text Data into JSON.

## Parameters

<table><thead><tr><th width="217">Parameter</th><th width="417.3333333333333">Description</th><th data-type="checkbox">Required</th></tr></thead><tbody><tr><td>String Contents</td><td>String to convert.</td><td>true</td></tr></tbody></table>

{% hint style="info" %}
You can utilize the Is JSON transform to test whether the string is valid JSON prior to parsing it with this transform.
{% endhint %}

## Usage

<details>

<summary>Example: Parsing a JSON String</summary>

Inputs:

**String Contents:**

```json
{"id":"676e061a-8004-4f60-ad37-cb0b2be25635","user":"Sean","age":32,"bio":"Hi, my name is Sean.\nI love hiking."}
```

</details>

## Results output

Result of Example:

```json
{
  "id": "676e061a-8004-4f60-ad37-cb0b2be25635",
  "user": "Sean",
  "age": 32,
  "bio": "Hi, my name is Sean.\nI love hiking."
}
```


---

# 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.rewst.help/documentation/automations/actions-in-rewst/transform-actions/parse-text-to-json-transform-action.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.
