Short answer: Drop the "Airtable → List Tables" 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') |
{"base_id": "appXXXXXXXXXXXXXX"}
{"tables": [{"id": "tblABC123","name": "Tasks","views": [{"id": "viwABC","name": "Grid view","type": "grid"}],"fields": [{"id": "fldXYZ","name": "Name","type": "singleLineText"},{"id": "fldABC","name": "Status","type": "singleSelect","options": {"choices": [{"name": "To Do"},{"name": "Done"}]}},{"id": "fldDEF","name": "Assignee","type": "singleLineText"}],"primaryFieldId": "fldXYZ"}]}
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.