Resources · Zapier integration

Algolia Zapier integrationAutomate Algolia with Zapier.

The Algolia Zapier integration gives you 2 triggers, 18 actions and 13 searches to feed, tidy and query your search indices without opening the dashboard. Here is what each one does, what it costs, and which ones you cannot undo.

See the 33 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Algolia Zapier integration actually does

It lets Zapier read from and write to your Algolia application without a developer in the loop. A Zap (an automation you build on Zapier: one trigger, then one or more actions that run each time that trigger happens) can push records into an index, adjust synonyms and rules, or look something up before the next step.

Three jobs come up again and again, and each maps to real operations. A cleaner index: Partial Update Record changes a few attributes on a record you already have, while Delete Records by Query removes everything matching a filter in one pass. Better search wording: Save Synonym and Batch Save Query Rules let a merchandiser or content lead adjust how queries behave without touching code. An export or a mirror: Browse Records pages through an index, and Add or Replace Record copies each record into a second index you keep for staging or backup.

Now the honest part. Both triggers here are polling triggers, so nothing reaches Zapier the second it happens in Algolia. Zapier also leaves the hard work to you: almost every write asks for the record, the rules or the settings as JSON, written by you or mapped from earlier steps. Several actions are destructive. Clear Index wipes every record, Delete Index removes the index and its settings, and Algolia itself flags that last one as irreversible.

If your team already runs other automation tools, the Algolia Make integration page covers the same app on Make, and our Zapier review weighs Zapier itself. The choice between the two depends on who maintains the Zap, not on a winner.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain English.

Trigger
The event in an app that starts your Zap. Once the Zap is on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that writes, sends or moves something in an app on your behalf.
Task
The unit Zapier bills. One task is one action your Zap completed successfully, and your plan counts those.
Polling trigger
A trigger Zapier checks on a timer. It asks the app for its latest items and keeps only the ones it has not seen yet.
Instant trigger
A trigger the app reports itself, the moment the event happens. Algolia has none on Zapier: both of its triggers poll.
Filter
A step that lets the Zap continue only when the data that arrived meets your condition, and stops it quietly otherwise.
Search step
A step that looks up something already in an app, so the steps after it can use what it found.
Cost

What Algolia on Zapier really costs

Algolia is not a premium app on Zapier, so it works from the free plan. The bill is counted in tasks, and only successful actions count.

  • Premium appNo, available on the free plan
  • Free plan100 tasks a month, unlimited Zaps
  • Free plan Zap sizeOne trigger and one action
  • Trigger costZero tasks

The trigger never costs a task, however often Zapier checks the index. Each action that goes through costs one; one that fails costs nothing. The free plan gives you 100 tasks a month, but it only builds two-step Zaps: one trigger, one action. Add a filter, a search or a second action and you have a multi-step Zap, which needs a paid plan. Every polling trigger is then checked at the interval of your plan, shown below.

Connect

Connect your Algolia account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need an Algolia account first, plus access to any application you do not own but want a Zap to touch.

  2. 02

    Pick Algolia

    Type Algolia in the search box of the dialog, select it, then click Add connection. A new tab opens on the Algolia side, where the actual sign-in happens.

  3. 03

    Sign in and grant access

    Sign in to Algolia in that tab and allow Zapier to use the account. The connection is saved once and reused by every step that talks to Algolia, in every Zap you build.

First Zap

Your first Zap: mirror selected records into a staging index

GoalRead the live index, keep only the records you care about, and copy them into a second index you can test against.

  1. 01

    Build the trigger

    Create a Zap, choose Algolia as the app and Browse Records as the event. Pick your connection, then type the exact Index Name of the live index you want to read.

  2. 02

    Test it on real data

    Click test. Zapier brings back the three most recent items from your account, so you map the next steps on a real record instead of a guess.

  3. 03

    Add a filter

    From the plus icon, add Filter. Choose a field from the record, the rule and the value. Use a text rule on text and a number rule on numbers, or it never passes.

  4. 04

    Add the copy action

    Add Algolia again with Add or Replace Record. Point Index Name at the staging index, never the live one, map the Object ID and build the Record (JSON) from the trigger's fields.

  5. 05

    Test, then publish

    Run the action once, check the record landed in staging, then Publish. The filter makes this a multi-step Zap, so it needs a paid plan.

Triggers

Algolia triggers on Zapier

2 events start a Zap when something happens in Algolia. Zapier checks for them at the interval your plan allows.

1

Browse Records

Polling trigger

In Zapier“Triggers when records are returned while browsing an Algolia index (paginated; useful for exports). Requires browse ACL. See Browse for records.”

Pages through one Algolia index and hands each record it returns to the rest of your Zap. It is the export door of this integration: whatever lives in the index can travel to the next step, one record at a time.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
you keep a catalog index up to date by hand and want each record it lists to reach a second index or a downstream step once.
Watch out
the key behind your connection needs the browse ACL, and the Index Name must be typed exactly as it appears in Algolia.
2

Get Recommend Rule

Polling trigger

In Zapier“Triggers when a recommendation rule is loaded from Algolia Recommend for your index, model, and rule ID. Requires settings API key ACL.”

Loads one recommendation rule from Algolia Recommend, the part of Algolia that suggests related products or content. You point it at a single rule, and your Zap receives that rule to work with.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a merchandising rule matters enough that you want to copy it, log it or act on it from another step.
Watch out
three fields are required, the Index Name, the Recommendation Model and the Rule ID, which is the rule's objectID as shown in your Algolia dashboard. The key also needs settings access.
Actions

Algolia actions on Zapier

Algolia gives you 18 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add or Replace Record

Action

In Zapier“Adds or fully replaces a record by object ID. Requires addObject ACL. See Add or replace a record.”

Writes a full record under an Object ID you choose. If that ID already exists, the whole record is swapped for the new one.

When to use it
your product catalog has stable IDs and you want the index to hold exactly what the source says.
Watch out
attributes you leave out of the Record (JSON) do not survive the replacement.
2

Batch Indexing

Action

In Zapier“Runs multiple add, update, or delete operations in one request. Requires addObject ACL. See Batch indexing.”

Sends several add, update or delete operations to one index in a single request, written as a JSON array.

When to use it
one event upstream should touch several records at once, for example a bundle and its parts.
Watch out
the Requests field mixes writes and deletes in one array, so a typo can remove a record you meant to keep.
3

Batch Save Query Rules

Action

In Zapier“Creates or replaces query rules in batch. Body is a JSON array of rule objects. Requires editSettings ACL.”

Creates or replaces several query rules, the merchandising rules that reshape results for given queries, in one request.

When to use it
a seasonal campaign brings a pack of promoted results that must go live together.
Watch out
Clear Existing Rules First replaces the entire ruleset, so rules missing from your array are gone.
4

Batch Save Synonyms

Action

In Zapier“Saves multiple synonyms in one request. Body is a JSON array of synonym objects. Requires editSettings ACL.”

Saves a whole set of synonyms on an index in one request, sent as a JSON array.

When to use it
a glossary kept elsewhere should land in Algolia in one go rather than line by line.
Watch out
with Replace All Synonyms switched on, every synonym not in your array disappears from the index.
5

Check Task Status

Action

In Zapier“Checks asynchronous indexing task status. See Check task status.”

Asks Algolia whether an indexing task has finished. Algolia indexes in the background, and each write returns a numeric task ID you can pass here.

When to use it
a later step should only run once a batch of writes is really live in the index.
Watch out
the Task ID is the numeric ID an indexing operation returned, so map it from the step that wrote.
6

Clear Index (Delete All Records)

Action

In Zapier“Removes all records from an index. Destructive. Requires deleteIndex (or equivalent) ACL. See Delete all records.”

Removes all records from an index in one go. Algolia labels it destructive.

When to use it
a full reload is planned and the old records must go before the new batch arrives.
Watch out
every record in the Index Name you type is removed, so double-check that name before publishing.
7

Clear All Synonyms

Action

In Zapier“Deletes every synonym on the index. Requires editSettings ACL.”

Deletes every synonym on an index at once, in a single action.

When to use it
you rebuild your synonym list from scratch and want an empty slate before Batch Save Synonyms runs.
Watch out
every synonym goes, not just the outdated ones, so keep it behind a filter.
8

Copy or Move Index

Action

In Zapier“Copies or moves an index within the app. Body example: {"operation":"copy","destination":"new_index"}. See Copy or move an index.”

Copies an index to a new name, or moves it there, inside the same Algolia application. You describe the operation and the destination in JSON.

When to use it
you want a snapshot of production before a big change, or to move a freshly built index to its final name.
Watch out
the Operation (JSON) field takes copy or move, so state clearly which of the two you mean.
9

Delete Records by Query

Action

In Zapier“Deletes records matching a query or filter. Heavy operation. Requires deleteIndex ACL. See Delete records matching a filter.”

Deletes every record matching a query or a filter in one heavy operation, described in Delete Parameters (JSON).

When to use it
a whole category or brand leaves the catalog and removing records one by one would cost a task each.
Watch out
Algolia calls it a heavy operation, and a filter that is too broad takes more than you planned.
10

Delete Index

Action

In Zapier“Deletes an index and its settings. Irreversible. Requires deleteIndex ACL. See Delete an index.”

Deletes an index together with its settings. Algolia describes this one as irreversible.

When to use it
temporary indices built for tests or one-off imports pile up and you want them gone.
Watch out
there is no undo, and the key needs the deleteIndex ACL, which is worth keeping off everyday connections.
11

Delete Query Rule

Action

In Zapier“Deletes one query rule. Requires editSettings ACL.”

Drops one query rule from an index, picked by its Rule ID.

When to use it
a promotion ends and the rule that pinned its products should go with it.
Watch out
the key needs the editSettings ACL, the same one every synonym and rule write asks for.
12

Delete Record

Action

In Zapier“Deletes one record by object ID. Requires deleteObject ACL. See Delete a record.”

Removes a single record from an index, found by its Object ID.

When to use it
an item is withdrawn from sale or an article is unpublished and should stop showing up in search.
Watch out
the key needs the deleteObject ACL, and the Zap must carry the right Object ID from an earlier step.
13

Delete Synonym

Action

In Zapier“Deletes one synonym. Requires editSettings ACL.”

Removes one synonym from an index, identified by its Synonym ID.

When to use it
a pairing created for a past campaign now sends shoppers to the wrong results.
Watch out
without Forward to Replicas, the synonym stays on your replica indices.
14

Batch Multiple Indices

Action

In Zapier“Batch add, update, or delete across multiple indices. Each request includes indexName, action, and body as needed. Requires addObject ACL.”

Runs add, update or delete operations across several indices in one call. Each request in the array names its own index.

When to use it
you keep one index per language or per region and a single change must reach all of them.
Watch out
there is no Index Name field here, the target index lives inside each request, so check every entry.
15

Partial Update Record

Action

In Zapier“Merges attributes into an existing record. Requires addObject ACL. See Add or update attributes.”

Merges a few attributes into a record that is already in the index and leaves every other attribute alone.

When to use it
only a price, a stock flag or a status changed and rewriting the full record would be overkill.
Watch out
it needs the Index Name, the Object ID and a Partial Record (JSON), so the Zap must already know which record it is updating.
16

Save Record (Auto Object ID)

Action

In Zapier“Adds a record; Algolia assigns object ID. Requires addObject ACL. See Add a new record.”

Drops a brand new record into an index and lets Algolia pick its ID. You only send the attributes, written as JSON.

When to use it
a new article or listing should become searchable and you have no ID of your own to give it.
Watch out
Algolia assigns the ID, so when your source already has stable IDs, Add or Replace Record is the better fit.
17

Save Synonym

Action

In Zapier“Creates or replaces one synonym. Requires editSettings ACL.”

Creates one synonym on an index, or replaces it if the same Synonym Object ID is already there.

When to use it
your support team spots shoppers typing a word your catalog never uses and wants it to match.
Watch out
tick Forward to Replicas if your replica indices must learn the synonym too.
18

Update Index Settings

Action

In Zapier“Updates index settings. Requires settings ACL.”

Changes the settings of an index from a Settings (JSON) object, the same settings Get Index Settings reads back.

When to use it
a team outside engineering needs to apply an agreed settings change without dashboard access.
Watch out
Forward to Replicas applies the change to replica indices as well, which you may not want.
Searches

Algolia searches on Zapier

13 search steps look for data that already exists in Algolia, so a later step can use it.

Algolia has 13 searches. In the editor they sit at the bottom of the Action event list, under SEARCH. Some fields also offer + Add search step, which inserts a search right before the current step and wires its result in. Algolia has no find-or-create entries, so none of these searches can create a missing item. Three settings decide what happens when the answer is not the one you expected.

1

Find Query Rule

Search

In Zapier“Gets one query rule by object ID. Requires settings ACL.”

Fetches one query rule by its Rule ID so the next steps can read it.

When to use it
before Delete Query Rule, to confirm the rule exists and log what it did.
Watch out
it needs settings access on the key, not just search access.
2

Find Record

Search

In Zapier“Retrieves one record by object ID. Requires search ACL. See Retrieve a record.”

Retrieves one record by its Object ID and hands its attributes to the steps that follow.

When to use it
you need the current version of a record before deciding whether Partial Update Record should run.
Watch out
it looks up an ID, not a text query, so you must already know the Object ID.
3

Find Synonym

Search

In Zapier“Gets one synonym by object ID. Requires settings ACL.”

Gets one synonym from an index by its Synonym ID.

When to use it
you want to check a synonym is in place before a campaign launches, and alert someone if it is not.
Watch out
leave Successful if no search results are found? off if a missing synonym should stop the Zap.
4

Get Index Settings

Search

In Zapier“Returns index settings. Requires settings ACL.”

Returns the current settings of an index, the same ones Update Index Settings writes.

When to use it
you keep a record of how an index was configured before someone changes it.
Watch out
the key needs the settings ACL, the same one every rule lookup asks for.
5

Get Records (Batch)

Search

In Zapier“Retrieves multiple records, optionally across indices. Requests look like { "indexName": "idx", "objectID": "id1" }. Requires search ACL.”

Retrieves several records in one call, optionally from different indices, each named by its index and Object ID.

When to use it
an order holds several product IDs and the next step needs all of their details.
Watch out
the Requests field is a JSON array, and every entry needs both the right index name and the right Object ID.
6

Get Recommendations

Search

In Zapier“Retrieve AI-powered product or content recommendations from Algolia Recommend.”

Asks Algolia Recommend for AI-powered product or content suggestions and returns them to your Zap.

When to use it
a follow-up message should carry related products picked by the same engine your site uses.
Watch out
it is a search step, so adding it makes the Zap multi-step and puts it on a paid plan.
7

List Indices

Search

In Zapier“Lists indices in the application. Requires listIndexes ACL. See List indices.”

Lists the indices in your Algolia application. No index name to type, since it covers them all.

When to use it
you audit what exists before a cleanup with Delete Index.
Watch out
the key needs the listIndexes ACL, a permission distinct from plain search.
8

Search for Facet Values

Search

In Zapier“Searches facet values for a configured attribute. Requires search ACL.”

Searches the values of one facet, a filterable attribute such as brand, inside an index.

When to use it
you want to check a brand or category value exists before writing a record that uses it.
Watch out
the Facet Attribute Name is required, typed exactly as the attribute is named, such as brand.
9

Search Index

Search

In Zapier“Runs a search query on an Algolia index. Requires search ACL. See Search an index.”

Runs a regular search query on one index, the way your site's search box would.

When to use it
a request comes in with a product name and the Zap needs the matching record.
Watch out
how close a match must be is decided by Algolia's settings, not by Zapier.
10

Search Multiple Indices

Search

In Zapier“Runs several index searches in one request. Each item in the array is one search (e.g. { "indexName": "products", "params": "query=phone&hitsPerPage=5" }). Requires search ACL.”

Runs several searches in one request, each with its own index and parameters.

When to use it
you look for the same term in a products index and an articles index at once.
Watch out
each search is an entry in a JSON array, so build and test that array carefully.
11

Search Query Rules

Search

In Zapier“Lists or searches merchandising and query rules. Requires settings ACL.”

Lists or searches the query rules and merchandising rules of an index.

When to use it
you review which rules are active before Batch Save Query Rules replaces them.
Watch out
by default only the first match moves on, so change If multiple search results are found? to see them all.
12

Search Recommend Rules

Search

In Zapier“Lists recommendation rules for a model. Requires settings ACL. See Search recommend rules.”

Lists the recommendation rules attached to one Recommendation Model on an index.

When to use it
you want an inventory of Recommend rules before editing a model or handing it to a colleague.
Watch out
both the Index Name and the Recommendation Model are required.
13

Search Synonyms

Search

In Zapier“Searches synonyms in an index. Requires settings ACL.”

Searches the synonyms already saved on an index.

When to use it
before adding a synonym with Save Synonym, check that a close one is not already there.
Watch out
only the Index Name is required, so narrow the search or expect many results.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps depending on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create on apps that support it. Algolia exposes no such variant, so you will not see it here.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When the Algolia Zap breaks

Most surprises with this app come from timing, from loops, and from actions that delete for good.

None of these show up as a clear error on day one. They show up as a task count that jumps, a record that never arrives, or an index that is suddenly empty. For a broken Zap that you cannot read, our Zapier troubleshooting page walks through it.

  • Old records are ignored

    A Zap only reacts to what happens after it is switched on. Records already in the index when you publish are not picked up, and moving that backlog is a separate job.

  • A Zap that feeds itself

    If the action writes into the very index Browse Records reads, the Zap can set itself off again and again and burn through your tasks. Write to a different index.

  • Large batches get held back

    After a bulk import, a trigger that suddenly returns a huge batch can be held back by Zapier's flood protection instead of running every record.

  • Deletes have no undo

    Clear Index, Delete Index and Delete Records by Query remove data in one move, and Algolia calls Delete Index irreversible. Keep them behind a filter.
Need help

Need help automating Algolia with Zapier?

A person reads every message.

FAQ

Algolia Zapier integration: questions people ask

01Is the Algolia Zapier integration free?
Yes, Algolia is not a premium app, so it works on the free Zapier plan. That plan gives you 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps: one trigger and one action. As soon as you add a filter, a search such as Find Record, or a second action, the Zap becomes multi-step and needs a paid plan. On the free plan, both Algolia triggers are checked every 15 minutes.
02How many Zapier tasks does an Algolia Zap use?
One task per action that completes successfully, and nothing else. Browse Records or Get Recommend Rule never cost a task, no matter how often Zapier checks. A Zap with three Algolia actions spends three tasks on each run. A failed action is not counted. That is a good reason to prefer Batch Indexing over several separate writes when one event changes many records, since one batch is one action. Searches such as Find Record are extra steps, which makes the Zap multi-step.
03Does Algolia send data to Zapier in real time?
No. Both Algolia triggers are polling triggers, so Zapier goes to check the index at a fixed interval set by your plan. On the free plan that interval is 15 minutes, on Professional it is 2 minutes, and on Team and Enterprise it is 1 minute. The interval cannot be switched to instant from the editor, because the app's own API decides how a trigger works. On paid plans, a check can also be run by hand from the editor.
04What do you need to connect Algolia to Zapier?
An Algolia account and access to the application you want to automate. In Zapier, open Apps, click + Add connection, choose Algolia, then sign in on the tab that opens and grant access. After that, check the permissions on the key: each operation asks for its own ACL, such as browse for Browse Records, editSettings for synonyms and rules, or deleteIndex for the wipes. The connection is then reused by every Algolia step in all your Zaps.
05Can a Zap delete an Algolia index by mistake?
Yes, if you give it the means to. Delete Index removes an index and its settings, and Algolia describes it as irreversible. Clear Index removes every record, and Delete Records by Query removes everything a filter matches. Keep them behind a filter, test them on a throwaway index first, and connect with a key that lacks the deleteIndex ACL when the Zap does not need it. Copy or Move Index can also snapshot the index before a risky change.
06What if the Algolia operation you need is not on Zapier?
Then look for the closest building block among the 33 that exist. Batch Indexing and Batch Multiple Indices accept raw JSON requests, which covers many adds, updates and deletes the named actions do not. Search Index or Search Multiple Indices can stand in for several narrower lookups. If nothing fits, the job needs another tool or direct work on Algolia, which is when outside help can save time. Check Task Status then tells you when those raw writes are live.
07Zapier, Make or n8n for Algolia?
It depends on who maintains the workflow and how much JSON they write. Zapier keeps the setup simple and gives you 33 ready operations, but multi-step Zaps need a paid plan and both triggers poll. Compare the three on who builds, how often data must move, and how you pay, rather than on a general ranking; the Algolia Make integration page lists what Make exposes for the same app. Whatever you pick, the destructive actions deserve the same care.
Same platform

Other docs you might need on this stack.

Browse all integrations