> For the complete documentation index, see [llms.txt](https://docs.diaflow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diaflow.io/workflow-builder/nodes/built-in-tools/convert-json-to-chart-data.md).

# Convert JSON to Chart Data

## Convert JSON to Chart Data

### What does it do?

The **Convert JSON to Chart Data** node turns structured data into chart-ready output. Think of it like a business analyst who looks at your numbers and suggests the best chart before your dashboard displays it.

#### Smart Features

* **Accepts input in different forms**: You can use data from an earlier node, paste structured data directly, or pass ready-made records.
* **Can pick the chart for you**: Choose **Auto detect** and Diaflow selects a chart style based on your data.
* **Can follow your chart choice**: If you already know the chart you want, Diaflow uses that type instead.
* **Uses a preview to map fields quickly**: It checks sample rows to match the right labels and values.
* **Returns the full dataset with the chart settings**: The result includes both the chart setup and all of your original records.

<figure><img src="/files/ZQiQGkk5Tv9DNyKgJlP9" alt=""><figcaption></figcaption></figure>

### Real-World Business Value

* Turn monthly sales records into a chart for a management dashboard.
* Visualize survey results by region, product, or customer segment without building charts by hand.
* Convert workflow results into chart-ready data before sending them to an app, report, or presentation step.

### Step-by-Step Setup

* In the **Input** field, select structured data from an earlier step using **@**.
* Make sure the input is a list of records, not a plain sentence or document.
* In **Chart type**, choose **Auto detect** if you want Diaflow to decide.
* Choose a specific option like **Bar chart**, **Line chart**, **Pie chart**, or **Donut chart** if you already know the best format.
* Run the workflow and review the output fields to confirm the selected chart type and mapped data fields.

<figure><img src="/files/rFdtMKqdNpEz0MjiYCtA" alt=""><figcaption></figcaption></figure>

### &#x20;The Transformation: Before & After

**Before**

```json
[
  { "month": "Jan", "revenue": 1200 },
  { "month": "Feb", "revenue": 1500 },
  { "month": "Mar", "revenue": 1700 }
]
```

**After**

```json
{
  "type_chart": "line-chart",
  "params": {
    "xField": "month",
    "yField": "revenue",
    "smooth": true
  },
  "data": [
    { "month": "Jan", "revenue": 1200 },
    { "month": "Feb", "revenue": 1500 },
    { "month": "Mar", "revenue": 1700 }
  ]
}
```

<figure><img src="/files/Yo5IpBgGRiPByLtc5Dq2" alt=""><figcaption></figcaption></figure>

### Tips &  Warnings for First-Timers

* Use a list of records as the input. A single plain object or empty data will fail.
* Keep your field names consistent across all rows. If later rows use different names, the chart choice may be wrong.
* Put the most representative rows first. Diaflow looks at the first few rows when choosing the chart.
* Flatten nested data before using this node. Deeply nested fields are not chart-friendly here.
* Avoid mixing text and numbers in the same field. Clean data gives better chart choices.
* If the output looks odd in **Auto detect**, pick the chart type manually.
* Large interactive chart experiences are better handled after this step. This node prepares chart data, but it is not meant for live chart editing.
* If your pasted input includes extra explanation text around the data, remove it first to avoid invalid input errors.

### Need help?

* Learn the basics in [How a node works](/getting-started/lets-start-with-the-basics/how-a-node-works.md)
* Build the full flow in [Create a workflow](/workflow-builder/create-a-workflow.md)
* Browse related nodes in [Component List](/workflow-builder/component-list.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.diaflow.io/workflow-builder/nodes/built-in-tools/convert-json-to-chart-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.