Short answer: Drop the "Algolia → Search Index" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
{"indexName": "{{trigger.indexName}}","query": "e.g. laptop","hitsPerPage": "{{trigger.hitsPerPage}}","filters": "e.g. price < 100 AND category:Electronics"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.