Algolia for n8n

Use the Algolia node for n8n to manage and query your indices from any n8n workflow. Whenever data changes in your other tools, such as a CMS, database, CRM, or spreadsheet, a workflow can add, update, or delete the matching records in Algolia, without writing custom code. Workflows can also search your indices, to route content, trigger alerts, or retrieve context for AI workflows. n8n is a workflow automation platform with a visual editor. You can use n8n Cloud or self-host n8n.

Before you begin

You need:

An n8n instance (Cloud or self-hosted)
On self-hosted n8n, community nodes turned on by an instance owner
Your Algolia application ID and an API key

Install the Algolia node

In the n8n workflow editor, click + to open the node panel.
Search for Algolia, then click Install node.

To install the node from the command line instead, for example when you manage a self-hosted instance, use the npm package name @algolia/n8n-nodes-algolia. See Install community nodes in the n8n documentation.

Connect your Algolia account

Add the Algolia node to your canvas, then click the node to open its parameters.
In the Credential for Algolia API menu, click Create new credential.
Fill in the credential fields:
- Application ID: your Algolia application ID
- Admin API Key: an Algolia API key with permissions for the operations you want to automate
Click Save.

The credential is stored in n8n and reused by every Algolia node in your workflows. Despite its name, the Admin API Key field accepts any Algolia API key. Only the API keys and Vaults operations need your Admin API key. For indexing and search, use a key restricted to the indices and operations your workflows need. When you save the credential, n8n tests it by listing your application’s API keys, which requires your Admin API key. With any other key, the test reports an error even though the credential is saved and your workflows run with it.

Available operations

The Algolia node covers the Search API. Pick a Resource, then an Operation.

Records

Add a new record (with auto-generated object ID): add a record and let Algolia assign its objectID
Add or replace a record: add a record, or overwrite the record with the same objectID
Add or update attributes: change some attributes of a record and leave the rest untouched
Retrieve a record: get one record by its objectID
Retrieve records: get several records, from one index or from different indices
Delete a record: delete one record by its objectID
Delete records matching a filter: delete every record that matches a filter
Delete all records from an index: empty an index but keep its settings, synonyms, and rules
Batch indexing operations on one index: add, update, or delete many records in one request
Batch indexing operations on multiple indices: the same, across several indices

Search an index: run a query against one index and return the hits
Search multiple indices: send several queries in one request
Search for facet values: find values of a facet attribute, for example to build a filter list
Browse for records: page through every record in an index

Indices

List indices: list the indices in your Algolia application
Copy or move an index: duplicate an index, or rename it
Delete an index: delete an index and its settings
Retrieve index settings: read the settings of an index
Update index settings: change the settings of an index
Check task status: find out whether an indexing task has finished

Synonyms

Create or replace a synonym: add one synonym, or overwrite it
Create or replace synonyms: add or overwrite several synonyms in one request
Retrieve a synonym: get one synonym by its ID
Search for synonyms: find the synonyms of an index
Delete a synonym: delete one synonym by its ID
Delete all synonyms: delete every synonym of an index

Rules

Create or replace a rule: add one rule, or overwrite it
Create or update rules: add or overwrite several rules in one request
Retrieve a rule: get one rule by its ID
Search for rules: find the rules of an index
Delete a rule: delete one rule by its ID
Delete all rules: delete every rule of an index

Dictionaries

Add or delete dictionary entries: change the entries of your plurals, segmentation, or stop word dictionaries
Search dictionary entries: find standard and custom dictionary entries
Retrieve dictionary settings: read which standard entries are turned off
Update dictionary settings: turn standard entries on or off for a language
List available languages: list supported languages, their dictionary types, and their number of custom entries

API keys

List API keys: list the API keys of your Algolia application
Create an API key: create a key with specific permissions and restrictions
Retrieve API key permissions: read the permissions and restrictions of a key
Update an API key: replace the permissions of a key
Delete an API key: delete a key
Restore an API key: restore a deleted key

Vaults

These operations configure the Algolia Vault firewall, an Enterprise add-on.

List allowed sources: list the IP addresses allowed to access your Algolia application
Replace allowed sources: replace the whole list of allowed IP addresses
Add a source: allow one more IP address
Delete a source: stop allowing an IP address

Advanced

Retrieve log entries: read your application’s API logs
Check application task status: find out whether an application-level task has finished

Build an indexing workflow

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

Create a new workflow

In n8n, create a workflow and give it a name.

Add a trigger

Add a trigger node for your data source, for example:

Webhook: your app calls n8n when content changes.
Schedule Trigger with a database or HTTP node: poll your source on an interval.
An app trigger such as Airtable, Notion, or Google Sheets: react to new or updated items.

Transform items into records

Add a Set or Code node to shape each item into a record. Keep only the attributes that are useful for searching, displaying, filtering, or ranking. Map the objectID attribute to a unique, stable identifier from your source data, such as a primary key.Algolia replaces a record that already has the same objectID, so a stable identifier means re-running the workflow updates your index instead of filling it with duplicates. For more information, see Prepare your records for indexing.

Send records to Algolia

Add the Algolia node and configure it:

Resource: Records
Operation: Batch indexing operations on one index, which adds or replaces every item in a single API request
Index name: your destination index

Test the workflow, then turn it on

Run the workflow once, then inspect the new records in the Algolia dashboard. If the records match what you expect, toggle Active to run the workflow automatically.

Handle deletions

To remove records when items are deleted at the source, add a second path or workflow that triggers on deletion and uses the Delete a record operation with the same objectID.

Search from your workflows

The Algolia node isn’t limited to sending data. Use the Search an index operation to retrieve records as part of a workflow, for example:

Deterministic workflows: search an index and act on the results, such as routing content, deduplicating entries, or enriching items in other tools.
Retrieval-augmented generation (RAG): search an index for relevant records and pass them as context to an LLM node, grounding responses in your own data.

Let an AI agent choose the queries

For workflows built around n8n’s AI Agent node, where the agent decides which tools to call, use the Algolia Public MCP server instead of the Algolia node. Connect it with n8n’s generic MCP Client Tool node. This lets agents search your indices and return recommendations, choosing their own queries and parameters at runtime. In short: the Algolia node when your workflow defines the query, the Algolia Public MCP server when the agent does.

Example workflows

Workflow	What it does	Nodes
CMS sync	Keeps search in sync with published content	Webhook trigger → transform → batch indexing
Search-driven alerts	Notifies you when new records match a query	Schedule Trigger → Algolia search → filter → Slack
Settings promotion	Automates configuration changes	Retrieve settings from a staging index → update settings on production
Web content indexing	Indexes pages from a site you don’t control	Schedule Trigger → a scraping node such as Firecrawl or HTTP Request → transform → batch indexing
RAG chatbot	Answers questions grounded in your indexed content	Chat Trigger → Algolia search → LLM node

Limitations

Records have a size limit that depends on your plan.
Batch operations are subject to the same limits as the API.
n8n executions have memory limits that depend on your plan or instance configuration. For large imports, prefer an API client or connector.

​Before you begin

​Install the Algolia node

​Connect your Algolia account

​Available operations

​Build an indexing workflow

​Handle deletions

​Search from your workflows

​Let an AI agent choose the queries

​Example workflows

​Limitations

​See also