Update Algolia with GitHub deployment outcomes
Keep deployment results searchable so the next decision starts with facts, not guesswork.
Trigger
New Deployment Status Created
Triggers when a new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses represent state transitions such as pending, in_progress, success, failure, error, inactive, and queued. The payload includes the status state, creator, environment, description, timestamps, and relevant URLs.
Action
Partial Update Objects
Tool to partially update multiple records in the specified index. use when you need to change only selected fields of many objects without replacing entire records. use after confirming objectids and desired updates.
Why this helps
A deployment record without its outcome still leaves teams digging through status pages and notifications.
- Clarify whether a release completed
- Keep operational history coherent
Setup
Build it in a few focused steps.
- 1Connect GitHub and Algolia to Notis once.
- 2Create an automation for deployment outcome updates.
- 3Tell Notis to refresh the matching Algolia deployment record when a new deployment status is created.
- 4Choose New Deployment Status Created and a run-report channel.
- 5Trigger a test deployment status and inspect the search result.
Questions about this workflow
Can reports go to my usual channel?
Yes. Select the channel where you want Notis to report automation runs.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Algolia. A trigger fires from one place; an action lands in another.
GitHub 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 Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
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.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
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.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
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.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
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.
GitHub 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.