ActionGristUpdated September 2026
How do I list Grist table records?
Short answer: You can list grist records in Grist by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Grist List Grist Records action to a workflow, map its 0 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Sample request
{}
Returns
{}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List Grist Records.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List Grist Records.
What does the List Grist Records action do in Grist?
Returns records from a Grist table. For "sync data from Grist to external system" workflows or for "fetch this Grist-managed config" lookups.
What inputs does List Grist Records require?
List Grist Records has no required inputs. Sensible defaults are applied if you leave fields blank.
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 Grist returns an error?
The run history shows the failed step with its input and the error message Grist 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 Grist Records support batch operations?
Run List Grist 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 Grist's rate limits.