- Integrations
- /
- Algolia
Algolia
Algolia search index management
Algolia is the hosted search-as-a-service platform that powers instant search on millions of sites. Tiny Command exposes five actions (no triggers — Algolia doesn't emit index-change webhooks), all focused on the index management side: List Indices (every index in the connected app), Add Object (insert or replace one record), Delete Object (by objectID), Clear Index (truncate every record in the index — destructive, use with care), and Search (run a query against an index, with all standard Algolia search params: query string, facetFilters, numericFilters, hitsPerPage, page, attributesToRetrieve). The connection uses an Algolia Application ID + Admin API key (or write-scoped key) from the Algolia dashboard. Search workflows commonly pair a CRM/Notion/Airtable trigger ("new product added") with Add Object to keep the search index in sync as the source of truth changes. For bulk operations (importing 10k records), Algolia recommends batch endpoints (/batch); Add Object is per-record and rate-limited at the standard limit, so workflows that need to ingest thousands of records should call the batch endpoint via HTTP action.
Do anything Algolia can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| 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. |
| Clear Index | 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. |
| Delete 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. |
| List 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. |
| Search 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. |
Pre-built Algolia workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Algolia once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Algolia field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Algolia integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Algolia to Tiny Command?
What Algolia triggers does Tiny Command support?
What Algolia actions can I run from a workflow?
Is the Algolia integration real-time?
Do I need to write code to use Algolia with Tiny Command?
How much does the Algolia integration cost?
More other apps people connect.
Same category as Algolia, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Algolia.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.