> For the complete documentation index, see [llms.txt](https://docs.zingy.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingy.ai/app-editor/page-flow/toolbox-blocks/data-table-data.md).

# Data Table : Data

{% hint style="info" %}
**Block Information**

Available in: Page Flow

Toolbox Category: Widget - Data Table

Block Type: [Output](/app-editor/page-flow/block-anatomy.md#output-block)

Output Type: [*object*](/app-editor/page-flow/references/value-types.md)
{% endhint %}

**`Data Table : Data`** is an [output block](/app-editor/page-flow/block-anatomy.md#output-block) that is used inside the *Selection Tasks* [flow parameter](/app-editor/page-flow/block-anatomy.md#flow-parameters) of the [Data Table Add Action](/app-editor/page-flow/toolbox-blocks/data-table-add-action.md) block.&#x20;

It provides an object representing the data associated with the [Data Table](/app-editor/page-editor/built-in-elements/data-table.md) widget, in the context of the specific custom action being handled by the [Data Table Add Action](/app-editor/page-flow/toolbox-blocks/data-table-add-action.md) block.&#x20;

The output is of type [*object*](/app-editor/page-flow/references/value-types.md) and is compatible with [Value Parameters](/app-editor/page-flow/block-anatomy.md#value-parameters) of type [*object*](/app-editor/page-flow/references/value-types.md) or of type [*any*](/app-editor/page-flow/references/value-types.md).

<div align="left"><figure><img src="https://3401585094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmnBepgycwgisXr9ya1N4%2Fuploads%2FHMJMbofMzUR89sobgSRM%2Fimage.png?alt=media&amp;token=cc08e2e0-43ac-4636-8359-9d1636ac5c3f" alt="" width="214"><figcaption><p>Data Table - Data block</p></figcaption></figure></div>

{% hint style="warning" %}
The Data Table : Data block only works when used inside the *Selection Tasks* [flow parameter](/app-editor/page-flow/block-anatomy.md#flow-parameters) of the [Data Table Add Action](/app-editor/page-flow/toolbox-blocks/data-table-add-action.md) block.
{% endhint %}

***

## Usage Example

The image below shows an example of the Data Table : Data block used inside the *Selection Tasks* [flow parameter](/app-editor/page-flow/block-anatomy.md#flow-parameters) of the [Data Table Add Action](/app-editor/page-flow/toolbox-blocks/data-table-add-action.md) block.

<figure><img src="https://3401585094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmnBepgycwgisXr9ya1N4%2Fuploads%2FNj5LixYHaTOQtoI6N6je%2Fimage.png?alt=media&amp;token=269f12e4-a680-401d-96f5-d17054593dba" alt=""><figcaption><p>Example of Data Table - Data</p></figcaption></figure>

The [Show Information Popup](/app-editor/page-flow/toolbox-blocks/show-information-popup.md) block is used to display the value of the Email field of the selected row.


---

# 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.zingy.ai/app-editor/page-flow/toolbox-blocks/data-table-data.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.
