Weekly Algolia synonym and rule suggestions in Slack

By General Input

Every Friday afternoon, get a Slack review list of proposed synonyms and query rules to rescue Algolia searches that returned zero results this week.

Integrations

  • Algolia
  • Slack

Type

Agentic Task

Categories

  • Marketing
  • Operations

Every Friday at 3pm in my timezone, run this workflow against my main Algolia index. The goal is a weekly, human-reviewable list of synonym and query rule fixes for the merchandising team. Do not apply any changes automatically.

Step 1. Pull the last 7 days of search analytics from Algolia. Use the Analytics: Top Searches with No Results operation to get the failing searches, and the Analytics: Top Searches operation to get overall volume context. Prioritize the zero-result queries with the highest search volume, since those are the ones costing us the most missed hits.

Step 2. For each high-volume zero-result query, reason about why it failed and propose one or more candidate fixes: a synonym (for example 'trainers' should also match 'sneakers'), a one-way synonym (for example 'parka' returns 'winter jacket' records but not vice versa), or a query rule (for example when the query contains 'gift for dad', pin the Father's Day category).

Step 3. Before including any candidate synonym in the review list, verify it is real. For each alternative phrasing you propose, call the Search Single Index operation against my main index using that alternative wording. If the alternative returns relevant records where the original returned zero, keep the suggestion. If the alternative also returns nothing useful, drop it. Do not guess.

Step 4. Compose a Slack message with a numbered list of up to 10 suggestions, ranked by the search volume of the failing query. For each item include: the failing search term and its 7-day search volume; whether this is a synonym suggestion or a query rule suggestion; the proposed change stated in plain language the merchandising team can act on; and one example matching record (title or objectID) you actually found under the alternative phrasing, so the reviewer can sanity-check the mapping before applying.

Step 5. Send the message with Slack's Send a Message operation to the merchandising review channel. End with a short reminder that these are suggestions for a human to apply, and that nothing has been changed in Algolia.

Hard constraint: do not call any Algolia write operation. Do not call Save Synonym, do not call Save Rule, do not call any indexing or settings write endpoint. The point of this workflow is a weekly reviewable suggestions list, not silent index changes. Human-in-the-loop is a feature, not a bug, because bad synonyms silently degrade relevance.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentWin back LiveChat visitors whose chats went unansweredChat quality review board for LiveChat support leadsWin back no-show and cancelled appointments every morningLive Loop returns analytics with product-level drill-downNewsletter pre-flight and approval board for Mailjet sendsTurn a prospect spreadsheet into personalized sequence enrollmentsMailjet email delivery lookup console for support teamsCatch feature flags that never got switched on in productionKajabi customer support console for member access fixes