Airtable
Create a record with typed fields. The personal access token needs schema.bases:read and data.records:write for the destination base. Enter the Base ID and Table Name or ID; the action discovers the table schema.
Map one form_field=Column Name per line. An explicit map sends only mapped fields; otherwise existing column names are matched. Numbers remain numbers, checkbox values become booleans, multi-selects remain arrays, and linked records accept record IDs. Dates must be ISO dates/date-times. Unsupported/computed fields produce a configuration error.
The metadata checkbox fills Form and Submitted At only when the columns exist. Unchecking it disables that metadata. No mandatory extra columns or attachment support are claimed. Schema metadata is cached for two minutes.
See delivery and retries for background behavior and failure reporting.
Mapping example
NAME=Name
EMAIL=Email
AGE=Age
CONSENT=Consent
INTERESTS=Interests
Configure Name as text, Email as email, Age as number, Consent as checkbox, and Interests as multiple select. Selected values remain arrays; the checkbox becomes a boolean and the number remains numeric.
Settings
| Setting | Purpose |
|---|---|
| Personal access token | Requires schema.bases:read and data.records:write |
| Base ID | Destination base (app...) |
| Table name or ID | Exact table name or tbl... identifier |
| Field mapping | Optional allowlist of form fields and destination columns |
| Submission metadata | Populate Form and Submitted At only when enabled and those columns exist |
| Run in the background | Queue using the saved submission |
Troubleshooting
- Give the token access to the selected base and both required scopes.
- Check destination names or use stable table IDs after renaming a table.
- Explicitly mapped columns must exist and be writable.
- Check checkbox, number, date, multiple-select, and linked-record values against their destination types.
- Date-only fields use YYYY-MM-DD. Date-time values use ISO timestamps; values without an offset use the WordPress site timezone.
- Metadata columns are optional. Disable metadata if the table should receive only form answers.
- Inspect the action log for errors. Transient failures may enter the queue; invalid credentials and invalid mappings need correction first.