Short answer: You can get record in Teable by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Teable Get Record action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 | – |
Record ID record_id | string | Required | The Record ID assigned by Teable. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
{"table_id": "{{trigger.table_id}}","record_id": "recXXXX"}
{"id": "recXXXX","fields": {"Name": "My Item"}}
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.