> ## Documentation Index
> Fetch the complete documentation index at: https://help.nextmatter.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data formats

> When you select data to reuse you can choose between providing data in JSON or plain format

When the data is used in other Next Matter steps or to complete integration, we recommend using the JSON format, as most systems parse and understand this format.

If you want the data to be provided in a human-readable format to display it to users, use the plain format.

When you send data from Next Matter to third-party tools, it's a good idea to check the tool's documentation to see which format is preferable.

## Differences in formats

<Info>
  In the case of the input types that are not listed here both options look the same.
</Info>

### Text and string input

<CodeGroup>
  ```JSON JSON theme={null}
  This is an example text with linebreaks\n\nand \"double quotes\"
  ```

  ```Text Plain theme={null}
  This is an example text with linebreaks

  and "double quotes"
  ```
</CodeGroup>

### Multi-value dropdowns and checklists

The examples are based on the `itemsSelected` and `itemsChecked` references. All other references for these inputs look the same.

<CodeGroup>
  ```json JSON theme={null}
  ["Option A", "Option B"]
  ```

  ```Text Plain theme={null}
  Option A, Option B
  ```
</CodeGroup>

### File and image uploads

The examples are based on the "files" and "images" reference. In the case of the `firstFile` reference there is no difference between JSON and plain.

<CodeGroup>
  ```json JSON theme={null}
  ["https://file1.com", "https://file2.com"]
  ```

  ```Text Plain theme={null}
  https://file1.com , https://file2.com
  ```
</CodeGroup>

### Tables

If you want to use table values as a data reference, you have the following options:

* Plain and JSON formats can be selected in the Body of Integration steps
* JSON format can be selected in other fields (for example form fields, or email messages)

There is no difference between JSON (other fields) and plain. The JSON that can be selected in the Body field contains escaped values.

The code example contains example values.

<CodeGroup>
  ```Text JSON (in Body of integration steps) theme={null}
  [[\"ONE\",\"Blue\"],[\"TWO\",\"Yellow\"],[\"ONE\",\"Blue\"],[\"TWO\",\"Yellow\"]]
  ```

  ```Text JSON (in other fields ) theme={null}
  [["ONE","Blue"],["TWO","Yellow"],["ONE","Blue"],["TWO","Yellow"]]
  ```

  ```Text Plain theme={null}
  [["ONE","Blue"],["TWO","Yellow"],["ONE","Blue"],["TWO","Yellow"]]
  ```
</CodeGroup>

<Tip>
  To send JSON table output to a Google Sheet using a custom integration, you must first parse the JSON to convert it from a string into a structured format. Currently, you cannot use the output in the Google Sheets no-code step.
</Tip>