ActionGristUpdated June 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.

List Grist Records in Grist — start free
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 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 Grist Records support batch operations?
Yes. Run List Grist Records inside a Loop node to process arrays. TinyCommand handles Grist's rate limits automatically so you don't have to throttle manually.
List Grist Records in Grist — start free