Real-timeupdates,triggeredfromAirtable

Cached sites are fast but go stale; uncached sites are fresh but slow and burn through Airtable's rate limits. Every Airtable-backed site picks its poison — or it used to.

VibeKit caches everything at the edge and gives the refresh switch to the people actually editing the data — inside Airtable, where they already work. Nobody has to open a dashboard, ping a developer, or wait for a redeploy.

Three ways to refresh, all from Airtable

• A button on the record. Drop a one-line formula into a Button field. Editors click it after changing a row and that record refreshes on the live site straight away — including for anyone looking at it right now.
• A button on the interface. Put a refresh URL behind a button in an Airtable interface to refresh a whole view (a list or grid) in one press — it's fresh the next time anyone loads it.
• No button at all. If records change by import, sync, or another automation, paste VibeKit's script into an Airtable Automation. Every change then clears its own record — hands-free.

The admin's Cache control tab lists every view and table your app reads and hands you the right snippet for each, ready to paste.

Precise, not scorched-earth

A record refresh touches that record. A view refresh touches that view. Nothing else is thrown away, so the rest of your site keeps serving instantly from cache. For lists that truly cannot wait — an event flipping to sold out — mark them high urgency and changes are pushed into the page as they happen (see live data).

Protected from runaway automations

If an automation starts firing refreshes too fast, VibeKit eases it off progressively and then fails the automation run so Airtable flags exactly which one misbehaved — your site stays up, and you find out without digging (see flood protection).