Check Algolia index readiness for new Jira projects
Make index readiness a visible part of project setup by checking the index named in the project context.
Trigger
New Project
Triggered when a new project is added in Jira
Action
Index Exists
Tool to check if an algolia index exists. use before performing index operations to prevent accidental index creation. example: indexexists(index name='products').
Why this helps
A project can begin work before its expected search index is confirmed, leaving teams to discover setup gaps later.
- Check whether a specified index exists.
- Expose missing index names early in project setup.
- Avoid guessing an index from a project name.
Setup
Build it in a few focused steps.
- 1Connect Jira and Algolia once in the Notis portal.
- 2Create an automation and name it for index readiness checks.
- 3In one instruction, tell Notis to check Index Exists for the Algolia index explicitly documented for the new project and report if that name is missing.
- 4Pick Jira New Project as the trigger and choose where run reports should go.
- 5Test with one real project that documents its expected index.
Questions about this workflow
Will this create an index if it is missing?
No. It checks whether the specified index exists and reports the result.
What if no index name is documented?
The workflow should report that the index name is missing and avoid guessing.
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.