Find customer context for repository notifications
Turn noisy notifications into a more informed next action.
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
List Conversations
Tool to list all conversations. use when you need to retrieve all conversation ids and metadata, optionally paginated.
Why this helps
Repository notifications compete for attention and rarely include the customer history behind them.
- Makes notifications more actionable
- Avoids manual inbox searching
Setup
Build it in a few focused steps.
- 1Connect GitHub and Superchat to Notis once.
- 2Create an automation in the portal.
- 3Tell Notis to retrieve relevant Superchat conversations when a repository notification arrives.
- 4Select Repository Notification Received and a run-report channel.
- 5Trigger a test notification and review the run.
Questions about this workflow
Can it focus on direct participation?
Choose the relevant GitHub notification setup when you create the trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Superchat. A trigger fires from one place; an action lands in another.
GitHub triggers
Superchat actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Contact
Tool to create a new contact. use when you need to register contact details before sending messages.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Template Folder
Tool to create a new template folder in superchat. use when you need to organize message templates into folders before populating them.
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.
Delete Webhook
Tool to delete a specific webhook by its id. use when you need to remove an obsolete or compromised webhook after confirming its id. example: delete webhook wh 12345.
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.
Get Contact
Tool to retrieve details of a specific contact by its id. use when you need to view a contact's information after verifying its existence. example: "fetch contact info for id abc123".
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get File
Tool to retrieve metadata of a specific file. use when you have the file id and need file information before downloading.
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.
Get User
Tool to retrieve details of a specific user by their id. use when you need to view or manage a user's profile. example: "fetch user info for id '123e4567-e89b-12d3-a456-426614174000'".
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 Channels
Tool to list all channels. use when you need to fetch available channels, optionally paginated by `limit`, `after`, or `before`.
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 Contacts
Tool to list all contacts. use when you need to fetch the full list of contacts for selection or reporting.
Connect any two apps with Notis in the middle.
GitHub and Superchat, 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 Superchat.