TActionTeableUpdated September 2026

How do I list records from a Teable table?

Short answer: You can list records in Teable by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Teable List Records action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Records in Teable — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Table ID
table_id
stringRequiredTeable table ID. Found in the URL of any table page.
View ID
view_id
stringOptionalOptional view filter. Applies view's sort/filter/hidden-fields settings.
Limit
take
numberOptionalMax records per page (1-2000).
Skip
skip
numberOptionalOffset for pagination.
Filter (TQL)
filter_by_tql
stringOptionalTeable Query Language filter, e.g. `{Status} = 'Done'`.
Sample request
{
"table_id": "tblXXXXXXXX",
"view_id": "viwXXXXXXXX",
"take": "{{trigger.take}}",
"skip": "{{trigger.skip}}",
"filter_by_tql": "{{trigger.filter_by_tql}}"
}
Returns
{
"records": [
{
"id": "recXXXX",
"fields": {
"Name": "Item 1",
"Status": "Done"
}
}
]
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Records.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about List Records.

What does the List Records action do in Teable?
Lists records from a Teable table with their field values and metadata. Pair with filters (or a view ID) to scope the result to just the rows you care about.
What inputs does List Records require?
Required: Table ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Teable returns an error?
The run history shows the failed step with its input and the error message Teable returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does List Records support batch operations?
Run List Records inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Teable's rate limits.
More actions

Other Teable actions.

List Records in Teable — start free