Check document types for GitHub repository notifications
Make important notifications easier to act on without opening another tool.
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
Get Document Types
Tool to retrieve a list of all document types available in the account. use when you need to view or select schemas for document processing.
Why this helps
Repository notifications can pile up and hide requests that need document handling.
- Keeps options one step away
- Helps prioritize follow-up
Setup
Build it in a few focused steps.
- 1Connect GitHub and Typless to Notis once.
- 2Create an automation in the portal or ask Notis in plain language.
- 3Use one prompt to retrieve Typless document types for a repository notification, select the notification trigger, choose a report channel, and test with one notification.
Questions about this workflow
Does it mark the notification read?
No. It retrieves Typless document types and reports them.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Typless. A trigger fires from one place; an action lands in another.
GitHub triggers
Typless actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Document Types
Tool to retrieve a list of all document types available in the account. use when you need to view or select schemas for document processing.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get User Profile
Tool to retrieve the authenticated user profile. use after authentication to confirm account details.
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.
Update User Profile
Tool to update the authenticated user's profile. use when user wants to change first name, last name, or email. example prompt: "update my email to alice@example.com"
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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.
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.
Connect any two apps with Notis in the middle.
GitHub and Typless, 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 Typless.