Airtable integration overview
The Airtable integration pushes your SKU.io data into your own Airtable base and lets a narrow, safe set of edits flow back — two-way, with no middleware in between. Use it to build custom dashboards, planning grids, and reports on top of live operational data.
What the integration does
SKU.io connects directly to your Airtable account as an OAuth client: you authorize your Airtable workspace, and SKU.io syncs records into the tables you choose. There is no third-party connector or paid automation layer to maintain — SKU.io reads its own data, transforms it into Airtable records, and upserts them on a schedule.
Every synced record carries a synthetic SKU.io ID key, so repeat syncs update the same Airtable row instead of creating duplicates. A subset of datasets also supports inbound enrichment: when you edit a whitelisted, non-operational field in Airtable, SKU.io can pull that change back in. Operational fields — status, dates, inventory, costs, and pricing — are never writable from Airtable. See Inbound safety and the field whitelist for the full boundary.
Where to find it
Airtable is not in the top-level navigation. Go to Apps & Integrations, then open the Airtable tile in the Data & Reporting category (the amber At logo). Its catalog description reads "Sync products, inventory & orders into Airtable — two-way, no middleware." From the tile you connect a new account or, if one already exists, deep-link into that instance's Dashboard.
Once connected, the integration has five tabs: Dashboard, Datasets, Inbound, Activity, and Settings.
The datasets it syncs
SKU.io exposes seven datasets you can map to Airtable tables. Each has a fixed field catalog that drives the mapping picker, the record transformer, and one-click table provisioning.
| Dataset | SKU.io source | Inbound editing? |
|---|---|---|
| Products | Products (incl. read-only analytics) | Yes — safe fields only |
| Inventory Levels | Per-warehouse inventory | No (outbound only) |
| Sales Orders | Sales orders | Yes — safe fields only |
| Sales Order Lines | Sales order lines | No (outbound only) |
| Purchase Orders | Purchase orders | No (outbound only) |
| PO Lines | Purchase order lines | No (outbound only) |
| Suppliers | Suppliers | Yes — safe fields only |
Only Products, Sales Orders, and Suppliers accept inbound changes, and each writes only a short whitelist of safe fields. The Products dataset also includes computed analytics (for example gross margin, days of cover, and 90-day sell-through) that are recomputed on every sync and are always outbound-only. Field-by-field details, cell types, and PII flags live in the Dataset and field reference.
Which approach should I use?
There are three ways to get data into Airtable. Pick the one that matches what you are building:
- One-click Ops Hub base — the fastest full setup. SKU.io provisions a ready-made base with pre-built tables, fields, and mappings for every dataset. Start here if you want a working two-way sync in minutes. See Create a ready-made Ops Hub base.
- A manual dataset mapping — point a dataset at an existing Airtable table, or sync only a subset of records. Use this when you already have a base laid out, or you want tighter control over which tables and fields sync. See Sync your data to Airtable.
- The Airtable: Write Rows automation node — push an ad-hoc report or a computed slice of records from an automation. Use this for one-off or workflow-driven writes rather than a standing dataset sync. See Write to Airtable from an automation.
Where to go next
For a working two-way sync in three steps, follow the golden path: Connect Airtable → Create a ready-made Ops Hub base → Monitor syncs and connection health to confirm the first sync ran. The connection re-verifies on its own — there is nothing to click to check it.
Start here
- Connect Airtable — authorize your Airtable account and create your first instance.
- Create a ready-made Ops Hub base — provision pre-built tables and fields in one step.
How-to guides
- Sync your data to Airtable — map datasets and run outbound syncs.
- Review changes from Airtable — approve inbound edits before they apply.
- Monitor syncs and connection health — track sync activity and reconnect when needed.
- Write to Airtable from an automation — push rows from the automation platform.
- Troubleshoot the Airtable integration — match a symptom to its cause and fix.
Concepts
- How Airtable sync works — the outbound record lifecycle explained.
- Inbound safety and the field whitelist — which fields Airtable can and cannot change.
- Reliability, limits, and sync-health alerts — rate limits, retries, and alerting.
Reference
- Dataset and field reference — every dataset, field, and cell type.
- Sync-mapping settings reference — schedule, delete mode, and mapping options.