ActionCodaUpdated May 2026

What tables exist in this Coda doc?

Short answer: Drop the "Coda → List Tables" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 6 Coda actions

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
Doc ID doc_id	string	Required	Doc ID. Example: AbCDeFGH

Sample request

{
  "doc_id": "e.g. AbCDeFGH"
}

Returns

{
  "items": [
    {
      "id": "grid-abc123",
      "name": "Tasks",
      "type": "table",
      "rowCount": 42
    }
  ]
}

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

Triggered by

Apps that pair well as the trigger for List Tables.

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

2 Google Sheets triggers

HubSpot → Coda

18 HubSpot triggers

FAQ

Questions about List Tables.

What does the List Tables action do in Coda?

Returns every table in a doc with name and row count. Useful for resolving table IDs at workflow-build time and for inventorying doc structure.

What inputs does List Tables require?

Required: Doc 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 Coda 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 Tables support batch operations?

Yes. Run List Tables inside a Loop node to process arrays. Tiny Command handles Coda's rate limits automatically so you don't have to throttle manually.

More actions