Short answer: Drop the "Airtable → List Records" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 | The Airtable base ID (starts with 'app') |
Table Name or ID table_id | string | Required | The table name (URL-encoded) or ID (starts with 'tbl') |
Filter Formula filterByFormula | string | Optional | Airtable formula to filter records |
Sort By Field sort_field | string | Optional | Field name to sort results by |
Sort Direction sort_direction | options | Optional | Sort Direction. Options: Descending, Ascending |
Max Records maxRecords | string | Optional | Maximum number of records to return |
View Name or ID view | string | Optional | Limit results to records in a specific view |
{"base_id": "appXXXXXXXXXXXXXX","table_id": "e.g. Tasks or tblXXXXXXXXXXXXXX","filterByFormula": "e.g. {Status} = 'Done'","sort_field": "e.g. Created","sort_direction": "{{trigger.sort_direction}}"}
{"offset": "itrXXX/recXXX","records": [{"id": "recABC123","fields": {"Name": "Task 1","Status": "Done","Assignee": "John"},"createdTime": "2025-01-01T00:00:00.000Z"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.