List Views
stackby.list_views
ActionDatabases & warehousesconnection required
Calls the Stackby API with the connection's credentials.
List one table's views, whose names a row listing can be filtered by.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Stackby
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- base_url, stack_id, table
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 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 |
|---|---|---|---|---|---|
stack_id Id of the stack to act on, from the stack's URL. Overrides the default stack id on the connection. | string | No | — | — | stqYn5AvM8wJP1pfjw |
table Name or id of the table to act on. Overrides the default table on the connection. | string | No | — | — | tbmtIz6IUXZ1ogNJeB |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"stack_id": "stqYn5AvM8wJP1pfjw",
"table": "tbmtIz6IUXZ1ogNJeB"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
views The views Stackby listed for this table. | array | — |
count How many views were listed. | number | — |
stack_id The stack the table belongs to. | string | — |
table The table whose views were listed. | string | — |
{
"count": 0,
"stack_id": "",
"table": "",
"views": []
}Related Stackby nodes
See List Views run in a workflow.
In a technical demo we add the Stackby connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.