Recheck Algolia results when a search incident changes
Check the current search response when an investigation ticket moves forward, without reopening the same tools manually.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Action
Search Algolia Index
Tool to perform a search on a specified algolia index. use after confirming the index name. example: searchindex(index name='contacts', query='apple', search params={'hitsperpage':10})
Why this helps
Search fixes are hard to assess when teams forget to rerun the original query after an issue update.
- Rerun the query recorded in the issue.
- Give investigators current results after ticket changes.
- Keep the check focused on the named index and query.
Setup
Build it in a few focused steps.
- 1Connect Jira and Algolia once in the Notis portal.
- 2Create an automation and name it for incident rechecks.
- 3In one instruction, tell Notis to rerun the issue's stated query against its named Algolia index and summarize returned results whenever the issue changes.
- 4Pick Jira Updated Issue as the trigger and choose where run reports should go.
- 5Test with one real incident that includes an index and query.
Questions about this workflow
Does this determine whether the fix worked?
It reports the current search results. Any expected baseline or pass criteria must be included in the issue or instruction.
What if someone updates an unrelated field?
The Jira trigger fires when an issue in the configured project is changed. Instruct Notis to report or skip when the issue lacks the required search details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Algolia. A trigger fires from one place; an action lands in another.
Jira triggers
Algolia actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add AB Test
Tool to create an ab test comparing search performance between two variants. use to test different index configurations or search parameters and measure impact on click-through and conversion rates.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Browse Algolia Index
Tool to retrieve all records from an index. use when you need to export or iterate through an entire index dataset.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Clear Objects
Tool to clear records of an index without affecting settings. use when you need to completely wipe all objects (e.g., after a bulk reindex) while preserving index configuration.
New Project
Triggered when a new project is added in Jira
Clear Rules
Tool to delete all rules in an index. use when you need to wipe all rules before re-creating them. use after confirming no critical rules require retention.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Clicked Object IDs
Tool to send a click event to algolia to capture clicked items. use immediately after a user click outside of search contexts to report click events.
Clicked Object IDs After Search
Tool to send a click event after a search response. use when you want to report which items a user clicked in search results.
Converted Object IDs
Tool to send a conversion event for items outside of search context. use when tracking conversions on category pages or external flows unrelated to algolia search.
Copy Index
Tool to copy the specified index to a new index. use when you need to duplicate an existing index including records, settings, synonyms, and rules after confirming source and destination names.
Connect any two apps with Notis in the middle.
Jira and Algolia, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Algolia.