> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/6.11/development/flow-portal-2/portlets/html-table.md).

# Html table

The HTML table allows for usage of HTML code to customize and present data. The source of the data can either be directly from a database or through a workflow. The HTML table portlet is, by default, wrapped as a table.

## General

General data is required for all portlets.

[General configuration](/6.11/development/flow-portal-2/portlets/common-configuration.md#general)

## Listeners

The portlet can listen to the following commands:

* On Row Selection
* On Refresh

[Listeners configuration](/6.11/development/flow-portal-2/portlets/common-configuration.md#listeners)

## Data

### Data source

The portlet data source configuration enables the portlet to execute specified queries towards the chosen database connector to fetch data, or fetch data from a workflow.

* Database: uses a flow connector to retrieve data from a database
* Workflow: runs a workflow to retrieve data

[Data source configuration](/6.11/development/flow-portal-2/portlets/common-configuration.md#database-source)

[Workflow source configuration](/6.11/development/flow-portal-2/portlets/common-configuration.md#workflow-source)

## Default presentation

<div align="left"><img src="https://543770944-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M0cMM76QMiiD7D7ZA7J%2F-M0cMY09VrTUHk-MfLWJ%2Fimage.png?alt=media&amp;token=5cb142ab-294f-48da-b543-039be107d754" alt=""></div>

## Content

In the table header and body sections, use HTML to configure the portlet content.

{% tabs %}
{% tab title="Content" %}

<div align="left"><img src="https://543770944-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M1VxJp1wHwux1zy-OVI%2F-M1VxpVbgqEFqvBycveE%2Fimage.png?alt=media&amp;token=6068ae63-6d5f-4978-81a5-3efabc1e8356" alt=""></div>
{% endtab %}

{% tab title="Preview" %}

<div align="left"><img src="https://543770944-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M1VxJp1wHwux1zy-OVI%2F-M1Vy5qDCSFXjvHqgarR%2Fimage.png?alt=media&amp;token=a6524808-b378-4762-a2f0-1f1b20a8af3a" alt=""></div>
{% endtab %}
{% endtabs %}

## Style

Change the header text color and add a header stripe by configuring style.

[Style configuration](/6.11/development/flow-portal-2/portlets/common-configuration.md#style)


---

# 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://help.novacuraflow.com/6.11/development/flow-portal-2/portlets/html-table.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.