Create a ready-made Ops Hub base
The fastest way to start syncing is the one-click Create SKU.io Ops Hub base action. It builds a brand-new Airtable base with one correctly-typed table per dataset, wires an enabled outbound mapping for each, and runs the first backfill for you — all as a single tracked job.
Before you begin
- Connect your Airtable account first. See Connect Airtable.
- Have your Airtable workspace ID ready. Find it in the workspace URL in Airtable (
airtable.com/<workspaceId>). The base is created inside that workspace. - Your Airtable grant must be able to create a base in that workspace.
Steps
- Go to Apps & Integrations → Airtable and open the Datasets tab.
- Select Create SKU.io Ops Hub base. It sits next to Add mapping in the header, and also appears in the empty state when you have no mappings yet. The Create SKU.io Ops Hub base dialog opens.
- In Airtable workspace ID, paste your workspace ID (for example
wspABC123...). This field is required — the Create base button stays disabled until you enter a value. - In Base name, optionally type a name for the new base. Leave it blank to use the default,
SKU.io Ops Hub. - In Order window (days), optionally set how many days of order history to backfill. Leave it blank to use the default of
90days. This limit applies to Sales Orders, Sales Order Lines, Purchase Orders, and PO Lines so the first backfill does not pull your entire order history. Datasets without dates (Products, Inventory Levels, Suppliers) ignore this value. - Select Create base. SKU.io creates the base, wires the mappings, and starts the backfill. You see the message "Building your Ops Hub base — track progress in the job tray."
- Open the job tray to watch progress. The job is named Create SKU.io Ops Hub base and reports per-dataset steps — "Creating the Airtable base…", then "Backfilling Products…", "Backfilling Inventory Levels…", and so on — with a progress bar that advances one step per dataset. When it finishes you see "Ops Hub base is ready."
What gets created
The base contains one table per syncable dataset: Products, Inventory Levels, Sales Orders, Sales Order Lines, Purchase Orders, PO Lines, and Suppliers. Each table is created with correctly-typed fields (number, currency, date/time, checkbox, and attachment columns where appropriate) and a key column named SKU.io ID. Every table description reads "Synced from SKU.io — do not edit the SKU.io ID field" — that key column is how SKU.io matches rows on later syncs, so leave it untouched.
Each mapping is created enabled, in the Outbound direction (SKU.io → Airtable), on an hourly schedule. Hard-delete datasets (Inventory Levels, Sales Order Lines, and PO Lines) default to the delete removal mode; the rest default to flag. For more on these settings, see the Sync-mapping settings reference.
If validation fails
If a value is rejected, the dialog stays open and shows the error directly under the affected field. Common causes:
- Airtable workspace ID is missing or longer than 64 characters.
- Base name is longer than 100 characters.
- Order window (days) is not a whole number, or is outside the allowed range of 1 to 3650.
Fix the highlighted field and select Create base again.
Next steps
- Sync your data to Airtable — trigger a manual sync or adjust a mapping.
- How Airtable sync works — understand upsert-by-key and archive handling.
- Monitor syncs and connection health — follow the backfill and later runs.
- Dataset and field reference — see every field in each table.