Connect incident.io to GitHub

When something happens in incident.io, Notis takes the next step in GitHub. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from incident.io to GitHub

View example

Assign GitHub incident issues to the active responder

Route a linked engineering issue to the person handling the incident, without reopening GitHub during a stressful handoff.

View example

Label GitHub issues from incident severity

Apply a consistent severity and incident label when your backend sends a new incident payload to Notis.

View example

Check whether incident fix pull requests merged

Run a daily check on the pull requests linked to open or recent incidents so closure does not depend on memory.

View example

Approve trusted hotfix workflow runs from forks

Use a verified incident webhook to approve the GitHub Actions run that is blocking a trusted forked hotfix.

View example

Cancel stale GitHub workflow runs after incident resolution

Stop obsolete deploy or diagnostic runs when an incident resolution webhook confirms they are no longer needed.

View example

Check private vulnerability reporting for incident repositories

Review a rotating set of incident-prone repositories weekly and report whether private vulnerability reporting is enabled.

View example

Grant a responder repository access during an incident

Add an approved specialist as a collaborator when an incident escalation webhook names the repository and responder.

View example

Add approved responders to the incident GitHub team

When an escalation webhook arrives, make the named approved person part of the incident response team in GitHub.

View example

Check incident responder access to key repositories

Run a monthly check that the people named in your incident roster can still collaborate on the repositories they may need.

Supported Triggers and Actions

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

incident.io triggers

GitHub actions

No triggers available yet

Accept a repository invitation

Accepts a pending repository invitation that has been issued to the authenticated user.

ActionInstant

List repositories starred by the authenticated user

Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.

ActionInstant

List stargazers

Deprecated: lists users who have starred a repository; use `list stargazers` instead.

ActionInstant

Star a repository for the authenticated user

Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.

ActionInstant

Add email for auth user

Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.

ActionInstant

Add app access restrictions

Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.

ActionInstant

Add a repository collaborator

Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.

ActionInstant

Add a repository to an app installation

Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.