List Tables
quickbase.list_tables
ActionDatabases & warehousesconnection required
Calls the Quickbase API with the connection's credentials.
List the tables in a Quickbase application.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Quickbase
- Secret shape
- the Quickbase user token, or {"user_token": "…"}
- Config it needs
- realm_hostname, app_id, base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 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 |
|---|---|---|---|---|---|
app_id Application to act in; overrides the application set on the connection. | string | No | — | — | bp2ryku2u |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"app_id": "bp2ryku2u"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
tables One object per table in the application. | array | — |
tables[].id The table id (dbid). | string | — |
tables[].name The table's name. | string | — |
tables[].keyFieldId Field id of the table's key field. | number | — |
count How many tables the application has. | number | — |
app_id The application that was read. | string | — |
{
"app_id": "",
"count": 0,
"tables": [
{
"id": "",
"keyFieldId": 0,
"name": ""
}
]
}See List Tables run in a workflow.
In a technical demo we add the Quickbase connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.