> For the complete documentation index, see [llms.txt](https://docs.aisera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisera.com/aisera-platform/ai-automation-optimize-flow/ai-workflow-studio/workflow-reference-guides/workflow-nodes/action-nodes/table-query.md).

# Table Query

The Aisera GenAI Platform supports custom tables through workflows. This feature can be used to define and maintain a schema or structure for these custom tables via configuration.

<div align="left"><figure><img src="/files/xVyxchV6OdLG9OYfKIA7" alt="" width="563"><figcaption></figcaption></figure></div>

The goal when using the **Table Query** feature is to make data from your custom tables available to your workflows. We support flow constructs that fetch data from custom tables.&#x20;

Flow authors can  define queries and filters to fetch the data. As the schema of the tables will be dynamic, the data is returned in JSON format.

<div align="left"><figure><img src="/files/d8SHvuTwRDmYIAhv3v1M" alt="" width="563"><figcaption></figcaption></figure></div>

The screenshot above shows the default actions that are available for your custom tables.&#x20;


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.aisera.com/aisera-platform/ai-automation-optimize-flow/ai-workflow-studio/workflow-reference-guides/workflow-nodes/action-nodes/table-query.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.