Algolia
Put Algolia to work on your own records, inside your rules, with a person approving what it changes.
25 ways to read, 7 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Algolia, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Send Insights eventsApproval by rule
- Save records in batchApproval by rule
- List A/B testsRead
Example flow
- Algolia · List A/B testsDone
- Algolia · Send Insights eventsNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Algolia.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Algolia
- Algolia's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Algolia test account before you go live.
For developers
Technical detail
Search, browse, read and save Algolia records, settings, synonyms and rules; read API keys, A/B tests, Analytics and Recommend; send Insights events.
Algolia API docs- Source actions
- 25
- Destination actions
- 7
- Data types
- 21
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Abtests2
- Get A/B testSource
One A/B test's variants, counts, rates and significance.
- List A/B testsSource
A/B tests with status, variants and significance (A/B testing API).
Analytics click through rate1
- Get click-through rateSource
Click-through rate with click and tracked search counts (needs click events).
Analytics conversion rate1
- Get conversion rateSource
Conversion rate with conversion and tracked search counts (needs conversion events).
Analytics no result searches1
- List searches without resultsSource
Most frequent searches that returned no results.
Analytics search count1
- Get search countSource
Total and daily number of searches for an index.
Analytics top filters1
- List top filter attributesSource
Attributes most often used as filters, optionally for one search.
Analytics top hits1
- List top hitsSource
Records most often returned in results, optionally for one search.
Analytics top searches1
- List top searchesSource
Most frequent searches with hit counts, and click and conversion rates when requested.
Analytics user count1
- Get user countSource
Total and daily number of unique users searching an index.
API keys1
- List API keysSource
API keys with their ACLs, indices, validity and limits. Key values are never returned to flows.
Events1
- Send Insights eventsDestinationNot retried automaticallyApproval before production
Sends up to 1000 click, conversion or view events (Insights API) for analytics, A/B testing, Recommend and personalization.
Indices1
- List indicesSource
Indices in the application with record counts, sizes and replicas.
Recommend rules2
- Get Recommend ruleSource
One Recommend rule by objectID.
- List Recommend rulesSource
Rules that promote, hide or filter recommendations for a model.
Recommendations1
- Get recommendationsSource
Recommendations from a trained Recommend model (related products, frequently bought together, trending items or facets, looking similar).
Record batch1
- Save records in batchDestinationProvider duplicate protectionApproval before production
Adds or replaces up to 500 records keyed by objectID in one indexing task (batch updateObject actions).
Record set1
- Get records by IDSource
Reads up to 500 records by objectID in one request; missing records return null.
Records5
- Get recordSource
Reads one record by objectID.
- Browse recordsSource
Exports all records of an index (optionally filtered) with a browse cursor.
- Search recordsSource
Full-text search with filters on one index.
- Update record attributesDestinationProvider duplicate protectionApproval before production
Sets the given attributes on a record; other attributes are kept.
- Save recordDestinationProvider duplicate protectionApproval before production
Adds or replaces a record with the given objectID.
Rules3
- Get ruleSource
Reads one query rule by objectID.
- List rulesSource
Query rules of an index with conditions, consequences and validity.
- Save ruleDestinationProvider duplicate protectionApproval before production
Creates or replaces a query rule by objectID.
Settings2
- Get index settingsSource
Searchable attributes, facets, ranking and other settings of an index.
- Update index settingsDestinationProvider duplicate protectionApproval before production
Changes the given index settings (searchable attributes, facets, ranking and so on); settings not sent are kept.
Synonyms3
- Get synonymSource
Reads one synonym by objectID.
- List synonymsSource
Synonyms of an index, optionally filtered by text and type.
- Save synonymDestinationProvider duplicate protectionApproval before production
Creates or replaces a synonym by objectID.
Tasks1
- Get task statusSource
Whether an indexing task has been published.
Access and limits
- Authentication
- Algolia application ID and API key
- Plans and access
- All Algolia plans, including Build (free). The API key's ACL must include search, browse, listIndexes, settings, addObject, editSettings, analytics and recommendation for the operations used; listing API keys needs the admin key.
- Test environment
- A free Build application can be used for testing.
- Rate limits
- Search operations are limited by plan; indexing is limited per application and key; the Analytics API allows 100 requests per minute per application. HTTP 429 when exceeded.
- Pagination
- Zero-based page numbers for search, index, synonym and rule lists; browse uses a cursor; Analytics and A/B test lists use limit and offset.
- Provider events
- Algolia does not deliver index webhooks. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Only the primary {appId}.algolia.net host is used for search and indexing; the -dsn read host and algolianet.com fallback hosts are not, so Nexra does not fail over between hosts.
- Writes are asynchronous: a taskID is returned and the change is searchable once the task is published.
- Partial updates accept plain attribute values only; built-in operations such as Increment are rejected because they are not safe to repeat.
- Search pagination is limited by the index's paginationLimitedTo setting (1,000 hits by default); use Browse records for full exports.
- Deletes (records, indices, synonyms, rules, Recommend rules, user tokens), delete-by-query, clear operations, index copy and move, and A/B test creation or stopping are intentionally not implemented.
- API keys are read only and their values are never returned; creating, updating, restoring and deleting keys is not implemented. Listing keys needs the admin API key.
- Index settings updates cannot change replicas, primary or mode.
- Dictionaries, query suggestions, personalization, multi-cluster, logs and the Analytics v3 patterns API are not exposed.
Developer reference
- Create the Algolia credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Algolia, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/algolia and the Connections API.