ActionNocoDBUpdated September 2026

How do I list NocoDB rows?

Short answer: You can list nocodb rows in NocoDB by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the NocoDB List NocoDB Rows action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List NocoDB Rows in NocoDB — start free All 5 NocoDB actions

List NocoDB Rows in NocoDB — start free

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 tableId	string	Required	Table ID. Example: tbl_abc123
Limit limit	string	Optional	Limit. e.g. "25"
Offset offset	string	Optional	Offset. e.g. "0"
Filter where	string	Optional	NocoDB filter syntax

Sample request

{
  "tableId": "e.g. tbl_abc123",
  "limit": "25",
  "offset": "0",
  "where": "e.g. (Status,eq,Active)"
}

Returns

{
  "list": [
    {
      "Id": 1,
      "Name": "John"
    }
  ],
  "pageInfo": {
    "page": 1,
    "pageSize": 25,
    "totalRows": 42
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List NocoDB Rows.

Any of these apps can fire this action as part of a workflow.

Google Sheets → NocoDB

2 Google Sheets triggers

HubSpot → NocoDB

18 HubSpot triggers

FAQ

Questions about List NocoDB Rows.

What does the List NocoDB Rows action do in NocoDB?

Paginated rows with NocoDB's filter syntax. For sync workflows that mirror NocoDB tables to other systems.

What inputs does List NocoDB Rows 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 NocoDB returns an error?

The run history shows the failed step with its input and the error message NocoDB 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 NocoDB Rows support batch operations?

Run List NocoDB Rows 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 NocoDB's rate limits.

More actions