> For the complete documentation index, see [llms.txt](https://docs.developers.symphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.developers.symphony.com/bots/messages/overview-of-messageml/messageml-basic-format-tags/tables.md).

# Tables

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

## Tags

MessageML supports the following tags to arrange information within a message using tables:

| Tags                                                | Description                      | Optional attributes                                                                      |
| --------------------------------------------------- | -------------------------------- | ---------------------------------------------------------------------------------------- |
| `<table>` `<tr>` `<td>text</td>` `</tr>` `</table>` | Render "text" in a table format. | <p>• <em><code>class</code></em><br>• <code>rowspan</code><br>• <code>colspan</code></p> |
| `<thead>`, `<tbody>`, `<tfoot>`                     | Table sections.                  | • `class`                                                                                |

## Examples

Here after you can find an example of a message sent by a bot and containing table tags as well as the structure of the messageML sent:

{% tabs %}
{% tab title="Message containing table tags" %}
![](https://3121587452-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB51RkjSmfA_ejydg4M-3415978100%2Fuploads%2FkwsL5uIuAK3SAtoqyx8X%2Fmml_tables.png?alt=media\&token=2cfa4cb9-f183-4448-bac9-fc713dfca87c)
{% endtab %}

{% tab title="messageML structure" %}

```markup
<messageML>
    <h1>Tables</h1>
    <p>This is a table:</p>
    <table>
        <thead>
            <tr>
                <td>Header column 1</td>
                <td>Header column 2</td>
                <td>Header column 2</td>
            </tr>
        </thead>
        <tbody>
            <tr>
                <td>Cell row 1 column 1</td>
                <td>Cell row 1 column 2</td>
                <td>Cell row 1 column 3</td>
            </tr>
            <tr>
                <td>Cell row 2 column 1</td>
                <td>Cell row 2 column 2</td>
                <td>Cell row 2 column 3</td>
            </tr>
        </tbody>
        <tfoot>
            <tr>
                <td>Footer column 1</td>
                <td>Footer column 2</td>
                <td>Footer column 2</td>
            </tr>
        </tfoot>
    </table>
</messageML>
```

{% endtab %}
{% endtabs %}
{% endtab %}

{% tab title="Mobile" %}

## Tags

MessageML supports the following tags to arrange information within a message using tables:

{% hint style="warning" %}
Supported on Android starting with the release of the Symphony Messsaging Mobile App v26.10. Support for iOS will be available in a later version.
{% endhint %}

| Tags                                                | Description                      | Optional attributes                                     |
| --------------------------------------------------- | -------------------------------- | ------------------------------------------------------- |
| `<table>` `<tr>` `<td>text</td>` `</tr>` `</table>` | Render "text" in a table format. | <p>• <code>rowspan</code><br>• <code>colspan</code></p> |

## Example

Message sent by a bot and containing table tags, as well as the structure of the messageML sent:

{% tabs %}
{% tab title="Message containing table tags" %}
![](https://3121587452-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB51RkjSmfA_ejydg4M-3415978100%2Fuploads%2FkwsL5uIuAK3SAtoqyx8X%2Fmml_tables.png?alt=media\&token=2cfa4cb9-f183-4448-bac9-fc713dfca87c)
{% endtab %}

{% tab title="messageML structure" %}

<pre class="language-markup"><code class="lang-markup">&#x3C;messageML>
    &#x3C;h1>Tables&#x3C;/h1>
    &#x3C;p>This is a table:&#x3C;/p>
    &#x3C;table>
        &#x3C;tr>
            &#x3C;td>Cell row 1 column 1&#x3C;/td>
            &#x3C;td>Cell row 1 column 2&#x3C;/td>
            &#x3C;td>Cell row 1 column 3&#x3C;/td>
        &#x3C;/tr>
<strong>        &#x3C;tr>
</strong>            &#x3C;td>Cell row 2 column 1&#x3C;/td>
            &#x3C;td>Cell row 2 column 2&#x3C;/td>
            &#x3C;td>Cell row 2 column 3&#x3C;/td>
        &#x3C;/tr>
          &#x3C;tr>
            &#x3C;td>Cell row 3 column 1&#x3C;/td>
            &#x3C;td>Cell row 3 column 2&#x3C;/td>
            &#x3C;td>Cell row 3 column 3&#x3C;/td>
        &#x3C;/tr>
    &#x3C;/table>
&#x3C;/messageML>
</code></pre>

<figure><img src="https://3121587452-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB51RkjSmfA_ejydg4M-3415978100%2Fuploads%2FIQQbCbfBmZiBSKHxAfBH%2Ftables.png?alt=media&amp;token=bf3d4095-d309-4776-afdd-c634254f203c" alt="" width="407"><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}
{% endtab %}
{% endtabs %}


---

# 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.developers.symphony.com/bots/messages/overview-of-messageml/messageml-basic-format-tags/tables.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.