Airtable: Create Multiple Records
Create multiple records (up to 10) in an Airtable base table in a single operation. More efficient than creating records one by one. Ideal for: batch imports, bulk data entry, syncing data from other sources.
Catalog action Integrations pipedream:airtable
Create multiple records (up to 10) in an Airtable base table in a single operation. More efficient than creating records one by one. Ideal for: batch imports, bulk data entry, syncing data from other sources.
At a Glance
| Field | Value |
|---|---|
| Action ID | airtable-create-multiple-records |
| Category | Integrations |
| Connector | pipedream:airtable |
| Requires gas | No |
| Funds movement | None declared |
| Tags | pipedream, integration, oauth, airtable, database, write, batch, bulk, import, sync |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
baseId | string | Yes | Airtable base ID (starts with 'app', e.g., 'appXXXXXXXXXXXXXX') |
tableId | string | Yes | Table ID or table name |
records | array | Yes | Array of records to create (max 10 records per request) |
typecast | boolean | No | Automatically cast field values (default: false) |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
success | boolean | Yes | Whether the records were created successfully |
data | object | No | Airtable API response data |
exports | object | No | Exported values from the action |
Examples
json{ "type": "airtable-create-multiple-records", "payload": { "baseId": "example-baseId", "tableId": "example-tableId", "records": [] }, "children": [], "connector": { "type": "pipedream:airtable", "id": "conn_pipedream_airtable" }}
bashcurl -X POST "https://api.b3os.org/v1/actions/airtable-create-multiple-records/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "baseId": "example-baseId", "tableId": "example-tableId", "records": [] }}'
Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.