List tables with the Superhuman Docs API
Lists the tables and views of a doc with id, name, type and parent page. Rows are written only to tables, not to views. Send nextPageToken as pageToken for the next page.
- Identifier
- coda_list_tables
The request
POST https://connect.reportei.com/api/tools/coda_list_tables/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"docId": "<docId>"
}
}Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| docId | string | Yes | Id of the doc, from List docs. |
| tableTypes | string | No | Types to include, separated by commas: table and view. Omit it to list both. |
| limit | integer | No | Tables per page. The default is 25. |
| pageToken | string | No | The nextPageToken of the previous response. |
Supported connections
Your customer connects their Superhuman Docs account once, with one of the modes below. The same connection serves every tool of the toolkit.
API key
Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.
The response
On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.
Ready for AI agents
This tool's input is a JSON Schema, available at GET /api/tools/coda_list_tables. It becomes your agent's tool definition with no conversion.
Other Superhuman Docs tools
- List docsGETLists the docs the user can access and has opened at least once, latest activity first, with id, name, owner, workspace and browserLink. Send nextPageToken as pageToken for the next page.
- Create docPOSTCreates a doc, empty or as a copy of another doc, in the My docs folder of the oldest workspace the user joined. Needs the Doc Maker role in the workspace.
- List pagesGETLists the pages of a doc with id, name, subtitle, parent and children. Send nextPageToken as pageToken for the next page.
- List page contentGETReturns the content of a page as plain text, element by element. Send nextPageToken as pageToken for the next part.
- Create pagePOSTCreates a page in a doc, or a subpage, with content in Markdown or HTML. The change is queued and shows up in a few seconds; the response has the id of the page. Needs the Doc Maker role.
- Update pagePUTRenames a page or adds content to it, at the end, at the start or replacing everything. The change is queued and shows up in a few seconds. Changing the name needs the Doc Maker role.
- List columnsGETLists the columns of a table with id, name and format. The column ids go in the cells of Create rows and Update row and in the query of List rows.
- List rowsGETLists the rows of a table or view, oldest first unless sortBy says otherwise, with id, name and the values keyed by column id. The data can lag a few seconds behind the doc; send nextPageToken as pageToken for the next page.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
