Delete Record
airtable.delete_record
ActionFiles & storageconnection required
Calls the Airtable API with the connection's credentials.
Delete one Airtable record by its record id.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- Airtable
- Secret shape
- the Airtable access token
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
base_id Airtable base id (app…), from the base's API docs URL or airtable.list_bases. | string | Yes | — | — | appAbCdEfGhIjKlMn |
table Table id (tbl…) or table name. An id survives a rename; a name does not. | string | Yes | — | — | Tasks |
record_id Record id (rec…) of the row to act on. | string | Yes | — | — | recAbCdEfGhIjKlMn |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"base_id": "appAbCdEfGhIjKlMn",
"record_id": "recAbCdEfGhIjKlMn",
"table": "Tasks"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The record id that was deleted. | string | — |
deleted True when Airtable confirmed the deletion. | boolean | — |
{
"deleted": false,
"id": ""
}Notes
- A deleted record is recoverable only from the base's trash, for a limited time.
- Airtable caps every batch write at 10 records per request. The batch nodes chunk for you and report how many calls they made in 'batches'; the calls are sequential and not a transaction, so a failure part-way leaves the earlier chunks committed and says how many got through.
- typecast is what lets a plain string be written into a single-select, date or number column. It is on by default, matching airtable.create_record.
- Reads page on an opaque 'offset' token, not a page number: feed the offset a call returns back into the next call while 'has_more' is true.
- The base/table/field nodes use Airtable's metadata API, which needs the 'schema.bases:read' (or ':write') scope on the personal access token. A token minted only for 'data.records:*' gets a 403 from them.
See Delete Record run in a workflow.
In a technical demo we add the Airtable connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.