List Bases: Airtable 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
Offset offset	string	Optional	Pagination cursor from previous response

Sample request

{
  "offset": "itr..."
}

Returns

{
  "bases": [
    {
      "id": "appABC123",
      "name": "My Project",
      "permissionLevel": "create"
    }
  ],
  "offset": null
}

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

FAQ

Questions about List Bases.

What does the List Bases action do in Airtable?

Lists all bases accessible to the authenticated user with name and permission level. Used to populate a base picker before drilling into tables.

What inputs does List Bases require?

List Bases 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 Airtable 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 Bases support batch operations?

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

More actions