Review Leverly retry history from a GitHub issue
When an ingestion issue assigned to you names a Leverly lead, Notis can retrieve reattempt history and report the matching details for triage.
Trigger
New Issue Assigned to Me
Triggers when a new issue is assigned to the authenticated user. Fires an event for each GitHub issue that is newly assigned to the authenticated user. Pull requests are automatically excluded -- only true issues are emitted. Issues can optionally be filtered by labels and state. The payload includes the issue number, title, body, state, labels, assignees, creator, repository details, and timestamps.
Action
List Reattempts
Tool to list all reattempts in leverly. use when you need to inspect the history of ingestion reattempts before taking further action.
Why this helps
Investigating a stalled ingestion can require switching from the engineering issue to Leverly just to inspect retry history.
- Bring retry context into the moment an ingestion issue is assigned.
- Keep the review read-only and scoped to the lead identifier explicitly named in the issue.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Leverly to Notis once in the portal.
- 2Create the automation in the portal or ask Notis for it in plain language.
- 3Tell Notis to retrieve Leverly reattempt history only for an assigned ingestion-support issue that explicitly names the lead identifier, and report only matching entries.
- 4Select GitHub New Issue Assigned to Me, optionally filtered to your Leverly-ingestion label, and choose a private channel for run reports.
- 5Test with one assigned issue containing a known Leverly lead identifier; confirm the result is read-only and limited to that lead.
Questions about this workflow
Will this stop or restart Leverly retries?
No. It uses the List Reattempts action for inspection only; it does not stop, start, or otherwise change retry processing.
What if the issue does not name a Leverly lead?
The instruction should skip the lookup and ask for the exact lead identifier rather than returning unrelated retry history.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Leverly. A trigger fires from one place; an action lands in another.
GitHub triggers
Leverly actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Reattempts
Tool to list all reattempts in leverly. use when you need to inspect the history of ingestion reattempts before taking further action.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Stop Leverly Reattempts
Tool to stop ongoing reattempts for a lead in leverly. use when you need to halt retries for a given reattempt id.
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.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire 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.
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.
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.
Connect any two apps with Notis in the middle.
GitHub and Leverly, 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 Leverly.