Skip to content
Notis

Start issue triage with more than a title

A new issue should arrive with enough context to decide what happens next.

Trigger

New Issue Created

Triggers when a new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assignee, creator, and mentioned user. The payload includes the issue number, title, body, state, labels, assignees, comment count, creator details, timestamps, and direct links to the issue on GitHub.

Action

/v1/enrich

Why this helps

Issue triage stalls when the report lacks ownership clues, related references, or useful background.

  • Improves first-pass triage
  • Reduces clarification loops
  • Makes backlog decisions easier

Setup

Build it in a few focused steps.

  • 1Connect GitHub and api.kadec0.xyz to Notis once through the portal.
  • 2Create an automation in the portal or ask Notis to create it in plain language.
  • 3Use this instruction: When a new GitHub issue is created, enrich it with relevant repository, technology, and public context, then return a concise triage brief with likely category and next question.
  • 4Choose the new issue trigger and a reporting channel.
  • 5Test with one real issue.

Questions about this workflow

Does it edit the issue?

No. It returns an enrichment brief for review.

Can it handle bug reports and requests?

Yes. Ask Notis to distinguish likely issue types in the instruction.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link GitHub to api.kadec0.xyz. A trigger fires from one place; an action lands in another.

GitHub triggers

api.kadec0.xyz actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

/v1/youtube

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

/v1/serp-batch

ActionInstant

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.

TriggerPolling

/v1/scrape

ActionInstant

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.

TriggerPolling

/v1/enrich

ActionInstant

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

/v1/serp-read

ActionInstant

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.

TriggerPolling

/v1/cve

ActionInstant

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.

TriggerPolling

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.

TriggerPolling

Connect any two apps with Notis in the middle.

GitHub and api.kadec0.xyz, 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 api.kadec0.xyz.