Process GitHub notifications with the rest of your work
The GitHub signals you care about arrive where your team already coordinates.
Trigger
Repository Notification Received
Triggers when a new or newly updated notification thread appears for a specific GitHub repository. Monitors notifications for issues, pull requests, commits, releases, check suites, security alerts, and other repository activity. Supports filtering by read/unread status and by direct participation. Requires a Personal Access Token (classic) with the ``notifications``
Action
Send Missive Message
Tool to send a new message in a missive conversation. use after selecting the target conversation id.
Why this helps
Repository notifications compete with email and chat, making it difficult to know which signal deserves attention.
- Reduces notification fragmentation
- Creates a shared triage surface
- Helps separate urgent signals from background noise
Setup
Build it in a few focused steps.
- 1Connect GitHub and Missive to Notis once through the portal.
- 2Ask Notis to send a Missive message for relevant new or updated notifications from a monitored GitHub repository.
- 3Select the repository notification trigger and choose the channel for run reports.
- 4Test with one unread repository notification.
Questions about this workflow
Can it monitor unread notifications only?
Yes. Configure the GitHub notification trigger with the appropriate read or unread filter.
Can it include only direct participation?
Yes. The trigger supports filtering for direct participation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Missive. A trigger fires from one place; an action lands in another.
GitHub triggers
Missive actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Analytics Report
Tool to create an analytics report. use when you need to generate a report over a specific time range with optional filters. returns a report id for later retrieval.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Draft
Tool to create a new draft in missive. use after preparing message details to save a draft (email, sms, whatsapp, or live chat) for later editing or scheduling.
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.
Send Missive Message
Tool to send a new message in a missive conversation. use after selecting the target conversation id.
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.
Create Webhook
Tool to create a webhook subscription. use after choosing event type and target url.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Delete Webhook
Tool to delete a webhook subscription by webhook id. use after confirming the webhook id; this operation cannot be undone.
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.
List Team Members
Tool to list members of a team. use when you need to retrieve all members for a specific team.
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.
List Missive Teams
Tool to list all teams. use when you need to retrieve and enumerate all teams available in missive.
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.
List Missive Users
Tool to list all users. use after authentication when you need to retrieve all users in the organization.
Connect any two apps with Notis in the middle.
GitHub and Missive, 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 Missive.