You can now configure a Table Gadget as an output in an integration.  This will allow you to pull data via an integration to display in a table gadget on a form.  Tables are now an option to select when configuring an integration output and upon selecting a Table Gadget as an Output you'll need to configure json for the table into the Table Config box:

Here is an example of the format that we would expect when configuring integration data to display in a table and what you would put in the Table Config of the output:.

[  {    "formKey": "N6TZ976AN6",    "id": "a5FD9TgPi",    "label": "Example Number Gadget",    "type": "Number"  },  {    "formKey": "G89eMQD5YY",    "id": "kbo16yrfs",    "label": "Example Text",    "type": "Text"  } ]

This is a flat array of objects. Each object in the array represents a different gadget/column within the table.
Keys breakdown:

formKey: this is the key you'll end up storing the data for this gadget on. Must be unique.
id: Similarly must be unique, this one is more for internal things to work correctly.
label: Optional, this is the text that shows up at the top of the associated column.
type: This must be a valid gadget type (IE: "Text", "Url", "Number", etc).

And in this example, this is how the data should be formatted when you send to our integration services for the integration to read the data correctly.  In this example the returned data is 2 filled out rows. You'll notice that within the first data key is an array of 2 objects. Each of these objects represents a row, and in each row object there's an id key as well as a data key that has a formKey for each of the gadgets you outlined above, followed by an assigned value that is associated with that gadget on that row.

{  "data": [    {      "data": {        "N6TZ976AN6": "42",        "G89eMQD5YY": "First row example"      },      "id": "B8vj6XWz9m"    },    {      "data": {        "N6TZ976AN6": "9001",        "G89eMQD5YY": "Second row example"      },      "id": "_uintwu6RF"    }  ] }

More information can be found in the Outputs section of the Create an API Integration article.