Keep GitHub security alerts from becoming forgotten tasks
When a vulnerability appears, Notis gives it a visible home in GitLab with the context your team needs to act.
Trigger
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.
Action
Create Project Issue
Tool to create a new issue in a gitlab project. use when you need to report a bug, request a feature, or track a task within a specific project.
Why this helps
Security alerts are easy to postpone when they arrive alongside feature work and customer requests.
- Centralize security follow-up in GitLab
- Reduce manual copying of alert details
- Make high-severity issues visible quickly
Setup
Build it in a few focused steps.
- 1Connect GitHub and GitLab to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create one in plain language.
- 3Tell Notis to create a GitLab issue for every new GitHub code scanning alert, including severity, rule, location, and source link.
- 4Choose the GitHub code scanning alert trigger and a channel for run reports, then test with one real alert.
Questions about this workflow
Can Notis include the vulnerable file and rule?
Yes. The plain-language instruction can ask Notis to include the alert’s rule, severity, location, and direct GitHub link.
Will this create duplicates for the same alert?
Notis can use the alert identity and existing GitLab context to keep repeated runs from creating unnecessary duplicates.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Gitlab. A trigger fires from one place; an action lands in another.
GitHub triggers
Gitlab actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive Project
Tool to archive a project. use when you need to mark a project read-only after finishing active development. call after confirming no further changes are required.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create GitLab Group
Tool to create a new group in gitlab. use when you need to establish a new group for projects or collaboration.
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.
Create Project
Tool to create a new project in gitlab. implements post /projects endpoint.
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 Project Issue
Tool to create a new issue in a gitlab project. use when you need to report a bug, request a feature, or track a task within a specific project.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create Repository Branch
Tool to create a new branch in a project. use when you need to create a new branch from an existing branch or a specific commit in a gitlab project.
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.
Delete Project
Tool to delete a gitlab project by its id. use when you need to remove a project, either by marking it for later deletion or deleting it immediately.
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.
Download Project Avatar
Tool to download a project’s avatar image. use when you need the raw avatar bytes after confirming the project exists.
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.
Erase Job
Tool to erase the content of a specified job within a project. use when you need to remove job artifacts and logs.
Connect any two apps with Notis in the middle.
GitHub and Gitlab, 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 Gitlab.