List Coda Docs: Coda action

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
Search Query query	string	Optional	Search Query. Example: Project Plan
Limit limit	string	Optional	Limit. e.g. "25"

Sample request

{
  "query": "e.g. Project Plan",
  "limit": "25"
}

Returns

{
  "items": [
    {
      "id": "AbCDeFGH",
      "name": "Q1 Planning",
      "owner": "john@example.com"
    }
  ]
}

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

FAQ

Questions about List Coda Docs.

What does the List Coda Docs action do in Coda?

Returns every doc the connected token can see. Useful for resolving doc IDs at workflow-build time. The token's access mirrors the user's doc-share permissions.

What inputs does List Coda Docs require?

List Coda Docs 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 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 Coda Docs support batch operations?

Yes. Run List Coda Docs 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