Create Record: Airtable action

Inputs

The fields this action accepts.

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.
Fields (JSON) fields	string	Required	Field values as a JSON object. Keys must match your Airtable column names exactly.

Sample request

{
  "base_id": "appXXXXXXXXXXXXXX",
  "table_id": "e.g. Tasks",
  "fields": "{\"Name\": \"New task\", \"Status\": \"To Do\", \"Assignee\": \"John\"}"
}

Returns

{
  "id": "recNEW123",
  "fields": {
    "Name": "New task",
    "Status": "To Do",
    "Assignee": "John"
  },
  "createdTime": "2025-01-15T12:00:00.000Z"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Create Record.

What does the Create Record action do in Airtable?

Creates a new record (row) in an Airtable table with the supplied field values. Field names must match the table's schema exactly (case-sensitive).

What inputs does Create Record require?

Required: Base ID, Table Name or ID, Fields (JSON). Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Airtable returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create Record support batch operations?

Yes. Run Create Record inside a Loop node to process arrays. Tiny Command handles Airtable's rate limits automatically so you don't have to throttle manually.

More actions