Respond faster when GitHub finds a leaked secret
A secret-scanning alert should trigger a clear response plan. Notis turns it into a GitLab issue immediately.
Trigger
New Secret Scanning Alert Detected
Triggers when a new secret scanning alert is detected in a GitHub repository. Monitors open secret scanning alerts and fires an event for each newly detected alert. Supports filtering by secret type (e.g., personal access tokens, AWS keys) and by token validity status (active, inactive, unknown). The payload includes the alert number, secret type, validity status, resolution state, timestamps, URLs, and flags for push protection bypass, public exposure, and multi-repo detection.
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
Founders may see a secret alert while multitasking and forget the rotation or containment work it requires.
- Create an immediate response queue
- Preserve alert and validity context
- Reduce the risk of missed credential rotation
Setup
Build it in a few focused steps.
- 1Connect GitHub and GitLab to Notis once through the portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3In one plain-language instruction, ask Notis to create a GitLab security issue for each new GitHub secret scanning alert with containment reminders and the source link.
- 4Select the secret alert trigger, choose a reporting channel, and test with one real alert.
Questions about this workflow
Can this distinguish active secrets?
Yes. Ask Notis to call out the secret type and validity status in the GitLab issue.
Does it rotate the credential automatically?
This workflow creates and organizes the GitLab follow-up; credential rotation should remain an explicit, reviewed action.
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
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.
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.
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 GitLab Group
Tool to create a new group in gitlab. use when you need to establish a new group for projects or collaboration.
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 Project
Tool to create a new project in gitlab. implements post /projects endpoint.
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.
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.
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.
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.
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.
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.
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.
Download Project Avatar
Tool to download a project’s avatar image. use when you need the raw avatar bytes after confirming the project exists.
Commit Event
Triggered when a new commit is pushed to a repository.
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.
Not just GitHub and Gitlab. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Gitlab.