List Tables
nocodb.list_tables
ActionDatabases & warehousesconnection required
Calls the NocoDB API with the connection's credentials.
List the tables of one base, with the table id every record node needs.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- NocoDB
- Secret shape
- the API token, or {"api_token": "…"}
- Config it needs
- base_url, base_id, table_id, workspace_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
base_id Id of the base whose tables to list. Overrides the base id on the connection. | string | No | — | — | pjcwv0q1v8p0k9x |
page Which page of tables to fetch, counting from 1. | number | No | — | ≥ 1 | — |
page_size How many tables per page. | number | No | — | 1–1000 | — |
include_m2m Include the junction tables NocoDB creates behind many-to-many links. | boolean | No | false | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"base_id": "pjcwv0q1v8p0k9x",
"include_m2m": false
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The objects NocoDB listed. | array | — |
count How many objects were listed. | number | — |
page_info NocoDB's own pageInfo object, when it sent one. | object | — |
base_id The base whose tables were listed. | string | — |
{
"base_id": "",
"count": 0,
"items": [],
"page_info": {}
}See List Tables run in a workflow.
In a technical demo we add the NocoDB connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.