Turn secret scanning alerts into response tasks
Make credential exposure follow-up visible, structured, and harder to forget.
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 Task
Tool to add a new task in a project. use when you have the project id and full task details ready.
Why this helps
A secret alert can require several response steps, but the urgency makes organized tracking difficult.
- Creates an immediate response record
- Preserves token type and validity context
- Supports calmer, more consistent remediation
Setup
Build it in a few focused steps.
- 1Connect GitHub and Bugherd to Notis once through the portal.
- 2Create the automation in the portal or ask Notis in plain language.
- 3Say: “When GitHub detects a new secret scanning alert, create a Bugherd task with secret type, validity, exposure flags, and alert link.”
- 4Select New Secret Scanning Alert Detected, choose your report channel, and test with a safe example.
Questions about this workflow
Will Notis expose the secret value?
No. The workflow should capture alert metadata and links, never the credential itself.
Can active tokens be prioritized?
Yes. Use GitHub filters or state that active credentials require urgent task wording.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Bugherd. A trigger fires from one place; an action lands in another.
GitHub triggers
Bugherd 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.
Add Guest to Project
Tool to add a guest (client) to a project. use when you want to add an existing client by id or invite a new client by email.
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.
Add Member to Project
Tool to add a member to a project in bugherd. use when you need to add an existing user to 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 Attachment
Tool to add a new attachment to a task using an existing url. use when you have project and task ids and the external file url ready.
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 Column
Tool to create a new column in a project. use when you need to add a custom workflow column after identifying the project id.
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 Comment
Tool to add a new comment to a task. use when you need to record discussion or feedback on an existing task.
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.
Create Project
Tool to create a new project. use when you need to initialize a project after gathering its name and url. example: "create a new project named 'my website' with url 'http://www.example.com'."
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.
Create Task
Tool to add a new task in a project. use when you have the project id and full task details ready.
Commit Event
Triggered when a new commit is pushed to a repository.
Create Webhook
Tool to create a new webhook for real-time event notifications. use when you need to configure a callback endpoint for task or comment events. example: "create a webhook for 'task create' events to be sent to 'https://example.com/webhook'."
Connect any two apps with Notis in the middle.
Not just GitHub and Bugherd. 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 Bugherd.