Search Records: 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	Airtable base ID (starts with 'app')
Table ID or Name table_id	string	Required	Table ID (starts with 'tbl') or table name
Filter Formula query	string	Optional	Airtable formula to filter records
Limit limit	number	Optional	Maximum results (max 50)

Sample request

{
  "base_id": "e.g. appABC123",
  "table_id": "e.g. tblXXXXXXXXXXXXXX",
  "query": "e.g. {Status} = 'Active'",
  "limit": "{{trigger.limit}}"
}

Returns

{
  "records": [
    {
      "id": "recABC123",
      "fields": {
        "Name": "John",
        "Email": "john@example.com"
      },
      "createdTime": "2026-01-15T10:00:00Z"
    }
  ]
}

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

FAQ

Questions about Search Records.

What does the Search Records action do in Airtable?

Searches records in an Airtable table using a filterByFormula expression. The right tool for upsert lookups by email or for cohort queries.

What inputs does Search Records require?

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

Yes. Run Search Records 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