Dataset to Airtable — Reliable Field Mapping
Export any Apify dataset into an Airtable table, mapping each field to the correct field type — with a per-item report of what mapped and what was skipped. Batched, rate-limit aware, no silent data loss.
Dataset to Airtable — Reliable Field Mapping returns 7 documented output fields, including itemIndex, status, airtableRecordId, mappedFields and skippedFields. Every field carries a declared type, a written description and an example value. 5 runs are recorded on Apify.
- 7
- Output fields
- 7
- Inputs
- 5
- Runs
- 2026-10-16
- Last run
01 — output
What it returns
Every field the extractor writes to its dataset, with its type, a written description and an example value.
| Field | Type | What it holds | Example |
|---|---|---|---|
| itemIndex | numbernull | Zero-based position of this item within its parent list. | 0 |
| status | stringnull | Outcome recorded for this row. | ok |
| airtableRecordId | stringnull | Airtable record identifier. | <airtableRecordId> |
| mappedFields | stringnull | Fields that were mapped to the destination. | ["title","price","sku"] |
| skippedFields | stringnull | Fields that were not mapped to the destination. | ["internalId"] |
| mappedCount | integernull | How many fields were mapped. | 3 |
| skippedCount | integernull | How many fields were skipped. | 1 |
02 — sample
One record
Assembled from the example values declared on the schema above, not invented at render time.
{
"itemIndex": 0,
"status": "ok",
"airtableRecordId": "<airtableRecordId>",
"mappedFields": "[\"title\",\"price\",\"sku\"]",
"skippedFields": "[\"internalId\"]",
"mappedCount": 3,
"skippedCount": 1
}03 — input
What you give it
| Input | Type | Description |
|---|---|---|
| apiToken | stringoptional | Secret — supply your own value. |
| baseId | stringoptional | The Airtable base ID (appXXXXXXXXXXXXXX), from your base URL. |
| tableName | stringoptional | The target table's name (e.g. 'Leads') or its table ID (tblXXXXXXXX). |
| datasetId | stringoptional | The Apify dataset to export (e.g. a scraper run's defaultDatasetId). Leave empty to use inline items. |
| items | arrayoptional | Rows to export if you have no dataset ID. Each object becomes one Airtable record. |
| fieldMapping | objectoptional | Map dataset fields to Airtable field names, e.g. {"soldPrice": "Price"}. Unmapped fields auto-match by name (case-insensitive). |
| maxItems | integeroptional | Cap on how many dataset items to write. Leave empty to export all. |
04 — run
Run Dataset to Airtable on your own input
It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.
05 — questions
Asked before running it
7 of 7 fields described
- What does Dataset to Airtable — Reliable Field Mapping return?
- It returns 7 documented output fields: itemIndex, status, airtableRecordId, mappedFields, skippedFields, mappedCount and skippedCount. Each field declares its type, a description of what it holds, and an example value.
- What input does Dataset to Airtable — Reliable Field Mapping take?
- All 7 inputs are optional and ship with usable defaults, so it runs as-is. They are listed with their types below.
- Does Dataset to Airtable — Reliable Field Mapping need an API key or login?
- Yes — apiToken is marked secret and must be supplied by you. Nothing else in the input schema needs credentials.
- How do I run Dataset to Airtable — Reliable Field Mapping?
- It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.