Create ServiceNow Incidents for Secret Scanning Alerts
Turn a frightening alert into a clearly owned response.
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 a record
Creates a new record in a specified servicenow table. this endpoint allows you to create a new record with the provided data in the specified table.
Why this helps
A leaked credential demands fast action, but the response can stall when the alert is buried among routine notifications.
- Creates an immediate response record
- Keeps secret type and validity context together
- Supports a repeatable security response
Setup
Build it in a few focused steps.
- 1Connect GitHub and ServiceNow to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Use this instruction: “When GitHub detects a new secret scanning alert, create a ServiceNow security incident with the secret type, validity status, repository, alert link, and recommended urgency.”
- 4Pick the GitHub secret scanning trigger, select the run-report channel, and test with one alert.
Questions about this workflow
Can the workflow distinguish active secrets?
Yes. Ask Notis to include the token validity status and make active or unknown secrets especially urgent.
Does this revoke the credential automatically?
No. This workflow creates the ServiceNow record; credential rotation or revocation remains a separate action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to ServiceNow. A trigger fires from one place; an action lands in another.
GitHub triggers
ServiceNow 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.
Attach file to record
Attaches a file to a specified record in a servicenow table. this endpoint allows you to attach a file with the provided details to the specified record.
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 a record
Creates a new record in a specified servicenow table. this endpoint allows you to create a new record with the provided data in the specified table.
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 a record
Deletes a record from a specified servicenow table. this endpoint allows you to delete a record with the provided id from the specified table.
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.
Find file
Finds a file in a specified servicenow table. this endpoint allows you to find a file with the provided name in the specified table.
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.
Get records
Retrieves a record from a specified servicenow table. this endpoint allows you to retrieve a record with the provided id from the specified table.
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.
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.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and ServiceNow. 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 ServiceNow.