Keep Algolia search in sync with new Airtable records
When your team adds a row in Airtable, we push it straight into your Algolia index so your site search stays current without manual syncs.
Airtable
AlgoliaOperationsMarketingData SyncEvery time a new record is created in a specific Airtable table, push it into my Algolia index so the search on my public site stays current.
Trigger: an Airtable poll on the new_record event, scoped to one base and one table that I pick when I set this up.
For each new Airtable record, call Algolia's Add or Replace Record operation on my target index. Use the Airtable record ID as the Algolia objectID so a future re-sync of the same record updates the existing Algolia entry instead of creating a duplicate.
Map a fixed set of Airtable fields into the Algolia record body. Start with Name, Category, Description, Image URL, and the public page URL. Copy them straight across, keeping the same field names on the Algolia side unless I say otherwise. Skip records where the Name field is empty so the search index does not fill up with placeholder rows.
I do not want a nightly full re-index and I do not want a manual sync button. The whole point is that new rows from content editors show up in site search within a minute or two of being saved in Airtable. A follow-up workflow can later extend this to updates (new_or_updated_record) and deletes; keep this one focused on inserts.
Additional information
What does this prompt do?
- Watches a specific Airtable table for new records and pushes each one into your Algolia index as soon as it appears.
- Uses the Airtable record ID as the Algolia object ID so any future re-sync updates the same entry instead of creating duplicates.
- Maps a fixed set of Airtable fields (name, category, description, image URL, page URL) into a clean Algolia record structure.
- Keeps your public search current in near real time, with no nightly full re-index or manual sync button to press.
What do I need to use this?
- An Airtable base with the table you want to keep in sync (a login with access to that base)
- An Algolia account and the index that powers your site search
- The list of Airtable fields you want searchable in Algolia (for example name, category, description, image, and page URL)
How can I customize it?
- Change which Airtable table or view is being watched.
- Adjust which fields are copied over and how they are named on the Algolia side.
- Point at a different Algolia index (for example a staging index while you test, then production).
FAQs
Will editing a row in Airtable later update the same Algolia entry?
What happens if the same record gets pushed twice?
Do I need a paid Algolia plan?
How quickly does a new Airtable row show up in search?
What if a record gets removed in Airtable? Does it disappear from search?
Related templates
Mark a row Approved in your content calendar and the post is scheduled on every channel you picked, at the time you picked, with no copy pasting.
Every new community post, review or job listing gets scored against your policy, labeled by topic, and only the risky ones ever reach your team.
Every weekday at 8am, get five creator posts that are outperforming their own usual numbers, with a one line reason to back each one.
Every four hours, log each arrival, departure and docking for your fleet in Airtable so laytime and demurrage claims rest on hard timestamps.
On the first Monday of each month, find the posts that actually performed, rewrite them with a new hook, and schedule them across the next four weeks.
Every Monday, each nutrition client gets a personalized five-dinner plan, shoppable recipe links, and one grocery list they can order in a single click.
Stop re-indexing Algolia by hand.
Let new Airtable rows land in your public site's search the moment content editors save them.