ActionAlgoliaUpdated September 2026
How do I empty an Algolia index?
Short answer: You can clear index in Algolia by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Algolia Clear Index action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 |
Sample request
{"indexName": "{{trigger.indexName}}"}
Returns
{"taskID": 12347,"updatedAt": "2026-04-12T10:00:00Z"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Clear Index.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Clear Index.
What does the Clear Index action do in Algolia?
Removes every record from the index while preserving index settings. Use carefully — destructive. Typical use case: "full rebuild from source-of-truth nightly" workflows where you clear then bulk-load.
What inputs does Clear Index require?
Required: Index Name. 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 run history shows the failed step with its input and the error message Algolia returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Clear Index support batch operations?
Run Clear Index inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Algolia's rate limits.
More actions
Other Algolia actions.
Action
Add Object to Index
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.
ActionDelete Object
Removes a single record by objectID. For deleting many records by criteria (e.g., "all records older than 30 days"), use the deleteBy endpoint via HTTP action which filters server-side.
ActionList Indices
Returns every index in the connected Algolia application with record count, last update timestamp, and configured settings summary. Useful for index inventory and for resolving index names in workflow setup.
ActionSearch Index
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.