Get Record: 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
Base ID base_id	string	Required	Base ID. e.g. "appXXXXXXXXXXXXXX"
Table Name or ID table_id	string	Required	Airtable table ID (starts with 'tbl') or the table's name. Find table IDs in the URL.
Record ID record_id	string	Required	The record ID (starts with 'rec')

Sample request

{
  "base_id": "appXXXXXXXXXXXXXX",
  "table_id": "e.g. Tasks",
  "record_id": "recABC123DEF456"
}

Returns

{
  "id": "recABC123DEF456",
  "fields": {
    "Name": "Task 1",
    "Status": "In Progress",
    "Assignee": "Jane"
  },
  "createdTime": "2025-01-01T00:00:00.000Z"
}

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

FAQ

Questions about Get Record.

What does the Get Record action do in Airtable?

Retrieves a single record by its ID from an Airtable table, returning all of its field values. The standard read after a trigger fires.

What inputs does Get Record require?

Required: Base ID, Table Name or ID, Record 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 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 Get Record support batch operations?

Yes. Run Get Record 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