Algolia for Zapier

Use the Algolia app on Zapier to manage and query your indices from any Zap. Whenever data changes in your other tools, such as a CMS, CRM, form builder, or spreadsheet, a Zap can add, update, or delete the matching records in Algolia, without writing custom code. Zaps can also search your indices, to route content, trigger alerts, or retrieve context for AI workflows. Zapier is a no-code automation platform. It calls a workflow a Zap: a trigger followed by one or more steps.

Before you begin

You need:

A Zapier account
Your Algolia application ID
A search API key with permissions for the read steps you plan to use
A write API key, if you use steps that create, update, or delete records, indices, settings, rules, or synonyms

Connect your Algolia account

There’s nothing to install: the Algolia app is part of Zapier’s built-in app catalog. Add a connection to your Algolia account, then select Algolia steps when building your Zaps.

In Zapier, go to the Apps page and click + Add connection.
Search for and select Algolia.
Enter your application ID and search API key, and optionally your write API key.
Click Yes, Continue to Algolia.

Zapier stores the connection and reuses it for every Algolia step in your Zaps.

Available steps

The Algolia app covers the Search API and the Recommend API. Each step needs a key with the ACL shown in parentheses. Missing permissions cause failed steps even when the connection test succeeds.

Triggers

Browse Records - Polling (browse): page through every record in an index
Get Recommend Rule (settings): get one Recommend rule by its ID

Searches

Search Index (search): run a query against one index and return the hits
Search Multiple Indices (search): send several queries in one request
Find Record (search): get one record by its objectID
Get Records (Batch) (search): get several records, from one index or from different indices
Search for Facet Values (search): find values of a facet attribute, for example to build a filter list
Get Recommendations (search): get related products, frequently bought together items, or trending items
List Indices (listIndexes): list the indices in your Algolia application
Get Index Settings (settings): read the settings of an index
Find Query Rule (settings): get one rule by its ID
Search Query Rules (settings): find the rules of an index
Search Recommend Rules (settings): find the Recommend rules of an index
Find Synonym (settings): get one synonym by its ID
Search Synonyms (settings): find the synonyms of an index

Actions

Add or Replace Record (addObject): add a record, or overwrite the record with the same objectID
Save Record (Auto Object ID) (addObject): add a record and let Algolia assign its objectID, which creates a duplicate if the same item changes twice
Partial Update Record (addObject): change some attributes of a record and leave the rest untouched
Batch Indexing (addObject): add, update, or delete many records in one request
Batch Multiple Indices (addObject): the same, across several indices
Copy or Move Index (addObject): duplicate an index, or rename it
Check Task Status (addObject): find out whether an indexing task has finished
Delete Record (deleteObject): delete one record by its objectID
Delete Records by Query (deleteIndex): delete every record that matches a filter
Clear Index (Delete All Records) (deleteIndex): empty an index but keep its settings, synonyms, and rules
Delete Index (deleteIndex): delete an index and its settings
Update Index Settings (editSettings): change the settings of an index
Batch Save Query Rules (editSettings): add or overwrite several rules in one request
Delete Query Rule (editSettings): delete one rule by its ID
Save Synonym (editSettings): add one synonym, or overwrite it
Batch Save Synonyms (editSettings): add or overwrite several synonyms in one request
Delete Synonym (editSettings): delete one synonym by its ID
Clear All Synonyms (editSettings): delete every synonym of an index

Build an indexing Zap

This example keeps an index in sync with content from another app. The same pattern works with any Zapier trigger.

Add a trigger

Create a Zap, then select the app and event that should update your index, for example:

Airtable, Notion, or Google Sheets: a new or updated item.
A form app such as Typeform: a new submission.
Schedule by Zapier: run on an interval.
Webhooks by Zapier: your app calls Zapier when content changes.

Send the record to Algolia

Add an Algolia action step, select the Add or Replace Record event, and configure it:

Index name: your destination index
Object ID: map a unique, stable identifier from your source data, such as a primary key
Record: map the attributes that are useful for searching, displaying, filtering, or ranking

Algolia replaces a record that already has the same objectID, so a stable identifier means each run updates your index instead of filling it with duplicates. To merge attributes into an existing record instead of replacing it, use Partial Update Record. For more information, see Prepare your records for indexing.

Test the Zap, then publish it

Test the Algolia step, then inspect the new records in the Algolia dashboard. If the records match what you expect, publish the Zap to run it automatically.

Index several items in one step

If your trigger returns several items as line items, use the Batch Indexing action to send them in a single request instead of one step run per item. To build the requests array, add a Code by Zapier step, or use a Looping by Zapier step to iterate over the line items.

Handle deletions

To remove records when items are deleted at the source, create a Zap that triggers on deletion and uses the Delete Record action with the same objectID. To remove every record matching a filter, use Delete Records by Query.

Search from your Zaps

The Algolia app isn’t limited to sending data. Use its search steps to retrieve records as part of a Zap, for example:

Deterministic workflows: use Search Index or Find Record and act on the results, such as routing content, deduplicating entries, or enriching items in other tools.
Retrieval-augmented generation (RAG): use Search Index to retrieve relevant records and pass them as context to an AI step, grounding responses in your own data.
Exports: use the Browse Records trigger to page through an index, for example, to back up records to a spreadsheet.

Let an AI agent choose the queries

For Zapier Agents and workflows where the AI decides which tools to call, use the Algolia Public MCP server instead of the Algolia app. Connect it with Zapier’s generic MCP Client (beta). This lets agents search your indices and return recommendations, choosing their own queries and parameters at runtime. In short: the Algolia app when your Zap defines the query, the Algolia Public MCP server when the agent does.

Example Zaps

Zap	What it does	Steps
CMS sync	Keeps search in sync with published content	New published entry → Add or Replace Record
CRM enrichment	Keeps a sales-facing index fresh	New or updated CRM record → Partial Update Record
User-generated content	Indexes approved submissions	New form submission → filter → Add or Replace Record
Web content indexing	Indexes pages from a site you don’t control	Schedule → a scraping app such as Firecrawl → Batch Indexing
RAG chatbot	Answers questions grounded in your indexed content	Chat trigger → Search Index → AI step

Limitations

Records have a size limit that depends on your plan, and other service limits can affect high-volume Zaps.
Batch requests are subject to the same limits as the API.
Every step run consumes Zapier tasks. To index several items per run, prefer one batch request.
For large imports, prefer an API client or connector.

​Before you begin

​Connect your Algolia account

​Available steps

​Build an indexing Zap

​Index several items in one step

​Handle deletions

​Search from your Zaps

​Let an AI agent choose the queries

​Example Zaps

​Limitations

​See also