Resources · Make integration

Algolia Make integrationAutomate Algolia with Make.

Can Make keep your Algolia indices up to date without a line of code? The Algolia Make integration gives you 6 modules: 4 actions and 2 searches. This guide shows how to link your account, then build a first scenario that pushes new items into an index.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Algolia Make integration do?

The Algolia Make integration links your Algolia account to Make, the no-code tool where you build a scenario (the automation itself, a chain of steps). Each step is a module: here, 4 actions that write or read records and 2 searches that return records or indices. Algolia has no trigger in Make, so something else starts the scenario.

A search index that follows your catalog. When another app registers a new product or article, Add a new record (with auto-generated object ID) sends it to your index, and Algolia creates the object ID for you.

Prices and stock that move without a full rewrite. Add or update record attributes changes only the attributes you send and leaves the rest of the record untouched, which suits a value that changes often.

A look before you write. Search Records pulls records from an index and Get a Record fetches a single one by its object ID, so a scenario can check what already exists before it adds anything.

What Make does not do here: no module watches Algolia for changes, so the scenario starts on a schedule or on another app's event. For anything the ready-made modules skip, Make an API Call reaches the rest of the Algolia API. New to the editor? The Make training covers the basics, and the n8n vs Make comparison helps if you are weighing both tools.

Connect

How do you connect your Algolia account to Make?

  1. 01

    Open the connection window

    In your scenario, add any Algolia module and click Create a connection. A connection is your Algolia account linked to Make once; every Algolia module you add later reuses it.

  2. 02

    Copy your credentials from Algolia

    In the Algolia dashboard, go to the API keys section from the account or settings area. Copy the API key and the Client ID shown on screen. The key needs the permissions your modules will rely on.

  3. 03

    Paste them and save

    Back in Make, the Connection name field is optional, but a clear name helps you spot the right account later. Paste the credentials you copied, or follow the on-screen instructions, and confirm.

First scenario

Your first scenario: send new items to an Algolia index

GoalWhen a new item appears in another app, Make adds it as a record in your Algolia index.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app that holds your items, such as a spreadsheet or an online store, and its trigger module.

  2. 02

    Add the Algolia action

    Click the + on the right of that first module, search for Algolia and choose Add a new record (with auto-generated object ID). Click Create a connection if you have none yet.

  3. 03

    Map the data

    Pick the index from the list Make shows once the connection works, then map values from the first module into the record. Each bundle, meaning each item passed along, becomes one record.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received. Open your index in Algolia and look for the new record.

  5. 05

    Schedule and switch on

    On the first module, open Scheduling: a new scenario runs every 15 minutes by default, and the Free plan cannot go faster. Keep it or adjust it, then switch the scenario on.

Modules

What can Make do with Algolia?

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

Algolia1

Add a new record (with auto-generated object ID)

Action

In MakeAdds a record to an index.

This module drops a fresh record into the index you choose, and Algolia gives it an object ID on its own, so you have nothing to invent. It is the natural end point of a scenario that feeds your search.

When to use it
a new product or article lands in another app and should become searchable on your site.
Watch out
it always creates, so running it twice on the same item gives you two records; for existing ones, pick Add or update record attributes.
Algolia2

Add or update record attributes

Action

In MakeAdds new attributes to a record, or updates existing ones. The module performs a partial update - preserves fields not specified in this request.

Change a price, a stock level or a label on a record that already exists, without resending everything. The module writes the attributes you give it, adds the missing ones, and keeps every other field as it was.

When to use it
a status or a value moves in your back office and the index should reflect it.
Watch out
the module has to know which record to touch, so place Search Records before it when the scenario does not know that yet.
Algolia3

Get a Record

Action

In MakeRetrieves one record by its object ID.

Fetch exactly one record by its object ID and receive it as a single bundle, ready for the modules that follow. Useful when an earlier step already knows which record matters.

When to use it
before an update, to read the current version of a record and compare it with the new data.
Watch out
it only works with an object ID; to find records by what they contain, Search Records is the module you want.
Algolia4

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Reach any endpoint of the Algolia API from your scenario, with the same connection as the other modules. It covers whatever the 5 ready-made modules leave aside, without a second account setup.

When to use it
you need an Algolia operation that has no module of its own in Make.
Watch out
here you write the request yourself, so keep the Algolia API documentation open next to the editor.
Algolia5

List Indices

Search

In MakeLists all indices in the current Algolia application.

Get the list of indices in your current Algolia application, one bundle per index. Handy to see what exists before a scenario writes anywhere.

When to use it
you run several indices, say one per language or per store, and the scenario has to work through them.
Watch out
as a search, it can return many bundles, and every module placed after it then runs once per index; each of those runs is an operation, the unit Make counts on your plan.
Algolia6

Search Records

Search

In MakeRetrieves records from an index.

Pull records out of an index so the rest of the scenario can work on them, whether you copy them elsewhere or update them one by one.

When to use it
you need existing records, and their object IDs, before Add or update record attributes can change them.
Watch out
the result can be zero, one or many bundles; with zero, the next modules have nothing to process, with many, they run once per record.
Need help

Need help automating Algolia with Make?

A person reads every message.

FAQ

Questions about Algolia and Make

01Is the Algolia Make integration free?
Yes, on the Make side. Algolia is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs spaced at least 15 minutes apart, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios, allow 40 minutes of execution and count usage in credits per month. You still need an active Algolia account, priced by Algolia itself.
02What does it take to connect Algolia to Make?
An active Algolia account and an API key with the permissions your modules need. In the Algolia dashboard, the API keys section of the account or settings area shows the API key and the Client ID; copy both. In Make, add any Algolia module, click Create a connection, give it a name if you like, and paste the credentials. All 6 Algolia modules then share that connection, so the setup happens once per account.
03Does the Algolia module react in real time?
No, because Algolia has no trigger in Make, so nothing inside Algolia can start a scenario. Two ways around it. Open the scenario with the trigger of another app, for instance the tool where your products or articles are created. Or let Make start it on a schedule, every 15 minutes by default, with Search Records or List Indices as the first module. On the Free plan, 15 minutes is the shortest interval; paid plans go down to 1 minute.
04What if an Algolia module is missing in Make?
Use Make an API Call. It calls any endpoint of the Algolia API with the connection you already set up, so an operation without a dedicated module stays within reach. The trade-off is that you write the request yourself, with the Algolia API documentation at hand. Keep one more thing in mind: the Make documentation for this app is AI-generated from the official Algolia docs and may contain mistakes, so verify important details with Algolia directly before you build around them.
05Make or n8n for Algolia?
It depends on where your other automations already live. Make gives you 6 ready modules for Algolia, a visual editor where you test each step with Run once, and a Free plan to start with 2 active scenarios. Algolia may also be available as an n8n node, so list the operations you need and check which tool covers them for your case. If your team already builds in Make, keeping Algolia there saves you from splitting related flows across two tools.