ActionAlgoliaUpdated May 2026

How do I search an Algolia index?

Q: What does the Search Index action do in Algolia?

Runs a query against an index with full search parameters — query string, facet filters, numeric filters, page size, attributesToRetrieve. The base read action for any "search-then-display" workflow that surfaces Algolia-indexed content downstream.

Q: What inputs does Search Index require?

Required: Index Name, Query. Every input accepts a static value or a variable from any upstream node in your workflow.

Q: Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

Q: What happens if Algolia returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Q: Does Search Index support batch operations?

Yes. Run Search Index inside a Loop node to process arrays. Tiny Command handles Algolia's rate limits automatically so you don't have to throttle manually.

Short answer: Drop the "Algolia → Search Index" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 5 Algolia actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Index Name indexName	string	Required	Index Name
Query query	string	Required	Query. Example: laptop
Hits Per Page hitsPerPage	number	Optional	Hits Per Page
Filters filters	string	Optional	Filters. Example: price < 100 AND category:Electronics

Sample request

{
  "indexName": "{{trigger.indexName}}",
  "query": "e.g. laptop",
  "hitsPerPage": "{{trigger.hitsPerPage}}",
  "filters": "e.g. price < 100 AND category:Electronics"
}

Returns

{
  "hits": [
    {
      "name": "Laptop Pro",
      "objectID": "1"
    }
  ],
  "page": 0,
  "nbHits": 1,
  "nbPages": 1,
  "processingTimeMS": 1
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Search Index.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Algolia

2 Google Sheets triggers

HubSpot → Algolia

18 HubSpot triggers

FAQ

Questions about Search Index.

What does the Search Index action do in Algolia?

Runs a query against an index with full search parameters — query string, facet filters, numeric filters, page size, attributesToRetrieve. The base read action for any "search-then-display" workflow that surfaces Algolia-indexed content downstream.

What inputs does Search Index require?

Required: Index Name, Query. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Algolia returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Search Index support batch operations?

Yes. Run Search Index inside a Loop node to process arrays. Tiny Command handles Algolia's rate limits automatically so you don't have to throttle manually.

More actions