Import Airtable records as WordPress posts and pages

Go to Airtable Sync → Airtable Config. Connect with OAuth, which is recommended for most sites, or use a Personal Access Token (PAT).

Option 1 Connect with OAuth Recommended

1. Click Connect with Airtable
2. Sign in to the account that can access your content base
3. Choose the bases to share and grant access
4. Confirm Connected via OAuth in WordPress

An import connection links one Airtable table to WordPress posts or pages. Mapped rows become real WordPress objects. Free allows one active Posts/Pages connection; Pro supports more.

1. Go to Airtable Sync → Import
2. Click Add Import Connection
3. Choose Posts (posts, pages, and custom post types)
4. Set Destination to Posts or Pages. Custom post types are Pro.
5. Select the Airtable base and table
6. Optionally select a view so only rows in that view import
7. Optionally open Filter records and add visual rules. An advanced formula is optional if the rules are not enough
8. Optionally add a connection name so you can find it later

If bases or tables do not load, reconnect under Airtable Config and confirm the token or OAuth grant includes this base.

Map at least the fields you need to publish. Unmapped Airtable columns are ignored, which is useful for internal fields such as owner, checklist, or “ready?”.

1. In Field Mappings, click Add Field for each pair you need
2. Choose the Airtable column, then the matching WordPress post field
3. Skip internal ops columns you do not want in WordPress
4. Use Custom Fields only when you need meta keys or ACF. Those destinations are Pro
5. Save after the required mappings look correct

Title is required for sensible permalinks. Status values should be draft, publish, pending, private, or future. Rich text, and long text that looks like Markdown, is converted to HTML. Plain text stays plain text.

• ID map (default safety): after the first successful import, later runs update the same WordPress object for that Airtable record instead of creating duplicates. If the mapped values have not changed, that row is skipped.
• Optional match by slug: useful when posts already exist in WordPress and you want the first import to attach to them by slug.
• Set default status behavior if a row omits status.
• Free schedules: manual, daily, weekly. Pro: as frequent as every 15 minutes, plus other intervals through twice daily.

Save the connection.

1. Click Dry run to preview the import without writing posts or pages
2. Open Airtable Sync → Sync Logs and review the dry-run result
3. Check for missing titles, unexpected status values, and the row count you expect
4. When the dry run looks right, return to the connection and click Import now

Dry-run and import results both appear in Sync Logs. Large tables process through background queues, so every row may not finish in one browser request. Recheck Sync Logs after the queue completes.

1. Stay in Airtable Sync → Sync Logs and open the Import now run
2. Check the import run status (success, warning, or error)
3. Drill into record-level detail when something failed (empty title, invalid status, attachment errors on Pro)
4. In WordPress, open a sample post or page and confirm title, content, slug, and status
5. Change one Airtable cell, run again, and confirm the same post updates