Review Algolia settings from new Jira configuration tickets
Bring current index settings into the ticket workflow when a configuration review is requested.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
Get Index Settings
Tool to retrieve the settings of a specified index. use when you need to inspect index configurations after creation or update.
Why this helps
Configuration reviews stall when someone has to leave Jira, locate the right index, and manually gather its settings.
- Retrieve current settings for a named index.
- Make configuration reviews easier to start.
- Surface missing index details in the run report.
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 configuration reviews.
- 3In one instruction, tell Notis to retrieve and summarize settings only for the Algolia index named in a configuration review issue.
- 4Pick Jira New Issue as the trigger and choose where run reports should go.
- 5Test with one real configuration review issue.
Questions about this workflow
Will this change the index settings?
No. It retrieves current settings for review.
Can it compare settings with a desired baseline?
Only if the expected settings are supplied in the Jira issue or automation instruction.
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.