TActionTeableUpdated May 2026

How do I list records from a Teable table?

Short answer: Drop the "Teable → List Records" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 Teable actions

Inputs

The fields this action accepts.

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

Field	Type	Required	Description
Table ID table_id	string	Required	Teable table ID. Found in the URL of any table page.
View ID view_id	string	Optional	Optional view filter. Applies view's sort/filter/hidden-fields settings.
Limit take	number	Optional	Max records per page (1-2000).
Skip skip	number	Optional	Offset for pagination.
Filter (TQL) filter_by_tql	string	Optional	Teable 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.

Google Sheets → Teable

2 Google Sheets triggers

HubSpot → Teable

18 HubSpot triggers

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Records support batch operations?

Yes. Run List Records inside a Loop node to process arrays. Tiny Command handles Teable's rate limits automatically so you don't have to throttle manually.

More actions