Connect GitHub to Worksnaps

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

View example

Turn new GitHub issues into Worksnaps tasks

Capture incoming engineering work as a focused Worksnaps task before it slips from view.

View example

Create review tasks for new pull requests

Make review work visible in Worksnaps as soon as a pull request opens.

View example

Turn assigned GitHub issues into personal tasks

Create a Worksnaps task whenever an issue is assigned to you.

View example

Update Worksnaps tasks after GitHub commits

Use new commits as a gentle signal to refresh the related Worksnaps task.

View example

Update tasks when pull request reviews arrive

Reflect review feedback in Worksnaps so follow-up work stays visible.

View example

Update tasks when pull requests merge

Mark related Worksnaps work as complete when a pull request is closed or merged.

View example

Create remediation tasks for code scanning alerts

Turn new security findings into a time-boxed Worksnaps task immediately.

View example

Create response tasks for secret scanning alerts

Create a Worksnaps task as soon as GitHub detects a potentially exposed secret.

View example

Create recovery tasks for failed deployments

Open a Worksnaps recovery task whenever a deployment status reports failure.

Supported Triggers and Actions

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

GitHub triggers

Worksnaps actions

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

Create Project

Tool to create a new project in worksnaps. use after gathering project details before logging time.

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

Create task

Tool to create a new task in a specified project. use after confirming project id exists.

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

Delete Task

Tool to delete a task from a project. use when you need to remove a task by its id after confirming the project context.

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

Get Project Details

Tool to retrieve details of a specific project. use when you have a project id and need its details.

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

Get Project Report

Tool to retrieve a project's time tracking report. use when you need summary of logged time per day for a project within an optional date range.

ActionInstant

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

Get Projects

Tool to retrieve a paginated list of projects. use after authenticating to list accessible projects.

ActionInstant

New Repository Collaborator Added

Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.

TriggerPolling

Get Task Details

Tool to retrieve details of a specific task within a project. use after confirming project id and task id.

ActionInstant

Commit Event

Triggered when a new commit is pushed to a repository.

TriggerInstant

Get Project Tasks

Tool to retrieve tasks for a specific project. use when you have a project id and need its tasks. example: 'get tasks for project 42'.

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.