Connect GitHub to Certifier

When something happens in GitHub, Notis takes the next step in Certifier. 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 GitHub to Certifier

View example

Issue a credential for a GitHub release

Turn a qualifying GitHub tag into a Certifier credential for a release milestone, using recipient and group details supplied in your instruction.

View example

Send a published credential after a release update

Use a GitHub release change as a reminder to send a corresponding credential that is already published in Certifier.

View example

Recognize a successful GitHub Actions run

When a monitored workflow run completes successfully, issue a Certifier credential for a qualifying achievement using your supplied group and recipient details.

View example

Check credentials after a pull request review

When a pull request review is submitted, retrieve the Certifier credential list so Notis can help check whether the relevant recognition is already recorded.

View example

Find a Certifier group after a code scanning alert

When GitHub reports a new code scanning alert, list Certifier groups to help Notis identify the group relevant to your security recognition process.

View example

Review credential designs for a new pull request

When a GitHub pull request is created, retrieve Certifier designs so Notis can surface the design that fits your stated recognition use case.

View example

Review credential interactions on demand

Start a Notis webhook when you need interaction history for a specific Certifier credential, with the credential details supplied in your instruction or request.

View example

Review the Certifier credential inventory on a schedule

On a schedule, retrieve the paginated Certifier credential list and have Notis summarize records relevant to the criteria in your instruction.

Supported Triggers and Actions

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

GitHub triggers

Certifier actions

Recurring trigger

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

TriggerScheduled

Send a Credential

Tool to send a published credential via email. use after confirming the credential is published.

ActionInstant

Webhook trigger

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

TriggerInstant

Create, issue, and send credential

Tool to create, issue, and send a credential in a single request. use when group id and recipient details are ready.

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

List Credential Interactions

Tool to list credential interactions. use when you need to retrieve interaction events for a specific credential, with optional filtering and pagination.

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

List Credentials

Tool to list credentials. use after authentication to retrieve paginated credentials.

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

List Designs

Tool to list all designs. use after authentication to retrieve certificate and badge designs with pagination.

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

List Groups

Tool to list all groups. use when you need to retrieve groups with pagination (limit and cursor).

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

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.