Pair failed checks with a research sanity check
A failed check tells you something changed. Let Notis show the research context before you start guessing.
Trigger
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.
Action
List Collection Requests
Tool to list all requests in a collection (paginated). use when you need to paginate through requests for a specific collection.
Why this helps
Technical failures prompt scattered debugging while product assumptions remain unexamined.
- Adds product context to failures
- Limits unstructured debugging
- Makes next actions clearer
Setup
Build it in a few focused steps.
- 1Connect GitHub and Asin data api to Notis once through the portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Describe the outcome as one instruction: List Asin requests related to the failed check suite and summarize what should be validated.
- 4Pick the check suite status or conclusion trigger and choose the run-report channel.
- 5Test with one failed suite.
Questions about this workflow
Can it run only on failure?
Yes. Configure the trigger and prompt to focus on failed, timed-out, or action-required conclusions.
Can it include the ref being checked?
Ask Notis to include the branch, tag, or commit reference in the report.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Asin data api. A trigger fires from one place; an action lands in another.
GitHub triggers
Asin data api actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Clear multiple collection requests
Tool to delete multiple requests from a collection by ids. use when you need to remove a selected set of request entries from an existing collection in a single call.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Collection Requests
Tool to list all requests in a collection (paginated). use when you need to paginate through requests for a specific collection.
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 Asin data api, 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 Asin data api.