NewBase
Get in touch

Airtable with Astro

Teams maintain the real content in Airtable and then keep a second copy of it somewhere else. An Astro site does not need the second copy: the build reads Airtable and renders the records, so there is one version of a row and it is the one in the base.

Get in touch

Airtable integrations like this usually take 3–6 days

How the handoff works.

  1. 01

    Record

    A row edited in Airtable

  2. 02

    Trigger

    The change leaves Airtable

  3. 03

    Map

    Fields matched to the collection

    Key handoff

  4. 04

    Build

    The page rendered from the record

  5. 05

    Verify

    The published item matches the row

Why this is the key handoff

Airtable is the desk. The build is the window. A row edited in Airtable is the version everybody works from, and the site should be showing that version rather than a copy somebody pasted a fortnight ago. Reading it at build time means there is no second copy to disagree with the first, which is the failure every two-way sync eventually has.

Three things that commonly go wrong.

  1. 01

    Field changes can break name-based mappings

    Field changes can break mappings: a sync matched on field names stops matching when somebody renames a column in a shared base. Mapping by field ID avoids it, and either way I validate the required fields on each run and surface a failure rather than letting it write nothing.

  2. 02

    Decide what happens when a source record is deleted

    A record removed in Airtable can drop its page, leave it behind as a redirect, or be ignored. A build that simply stops rendering it leaves the old address returning a 404 to anyone holding the link, so the deletion needs a decision rather than a default.

  3. 03

    Large syncs need batching and retries

    Airtable pages its records and rate limits its API, so a base of any size is a queue rather than a loop. Past a certain size the records are better cached between builds than fetched fresh every time, because a build that takes four minutes to read a database is a build nobody runs.

What is included.

  • Airtable records read at build time, or synced into Content Collections

  • Field mapping for text, images, references, select fields and publish state

  • Deletes, renames and archived records handled deliberately

  • Draft and live behavior that matches the team's workflow

  • Sync logs and alerts for failed updates

Wire up something else?

Reach out and see if we are a good fit.

Get in touch

Currently booking two to four weeks out.