Short answer: Drop the "Airtable → Delete Record" 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 | 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 | Airtable record ID — starts with 'rec'. |
{"base_id": "appXXXXXXXXXXXXXX","table_id": "e.g. Tasks","record_id": "recABC123DEF456"}
{"id": "recABC123DEF456","deleted": true}
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.