Add Object to Index: Algolia action

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
Object ID objectID	string	Required	Object ID
Object Data data	json	Required	Object Data. (JSON object). e.g. "{"name":"Product","price":29.99}"

Sample request

{
  "indexName": "{{trigger.indexName}}",
  "objectID": "{{trigger.objectID}}",
  "data": "{\"name\":\"Product\",\"price\":29.99}"
}

Returns

{
  "taskID": 12345,
  "objectID": "1",
  "updatedAt": "2026-04-11T10:00:00Z"
}

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

FAQ

Questions about Add Object to Index.

What does the Add Object to Index action do in Algolia?

Inserts or replaces a single object in the index (Algolia upserts on objectID — same ID overwrites). For bulk operations on hundreds-plus records, prefer the batch endpoint via HTTP action which is much cheaper against the rate limit.

What inputs does Add Object to Index require?

Required: Index Name, Object ID, Object Data. 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 Add Object to Index support batch operations?

Yes. Run Add Object to 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