Short answer: Drop the "Teable → List Records" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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'`. |
{"table_id": "tblXXXXXXXX","view_id": "viwXXXXXXXX","take": "{{trigger.take}}","skip": "{{trigger.skip}}","filter_by_tql": "{{trigger.filter_by_tql}}"}
{"records": [{"id": "recXXXX","fields": {"Name": "Item 1","Status": "Done"}}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.