Keep new code scanning alerts in view
Security findings should not rely on memory.
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
Report Exception
Tool to report an exception notice to Honeybadger. Use when sending error details (stack trace, context) for diagnostics.
Why this helps
Security alerts can be easy to postpone when there is no single place to review them with other technical risks.
- Centralizes security findings with production diagnostics
- Keeps severity and rule context attached
- Creates a reviewable record for follow-up
Setup
Build it in a few focused steps.
- 1Connect GitHub and Honeybadger to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to build it conversationally.
- 3Use this instruction: “When GitHub creates a code scanning alert, report an exception to Honeybadger with the rule, tool, severity, file location, repository, and alert link.”
- 4Select the code-scanning-alert trigger, choose a run-report channel, and test with one real alert.
Questions about this workflow
Can I limit this to high-severity findings?
Yes. Configure the GitHub trigger for the severity range that matters to your team.
Does this replace GitHub security workflows?
No. It adds a Honeybadger record so important findings are harder to miss.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Honeybadger. A trigger fires from one place; an action lands in another.
GitHub triggers
Honeybadger 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.
Report Check-In
Tool to report a check-in (ping) to Honeybadger. Use when monitoring scheduled tasks to signal they're running on time.
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.
Report Deployment
Tool to report a new deployment to Honeybadger. Use after a successful release to notify Honeybadger of the deployment.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Report Event
Tool to send custom events to Honeybadger Insights. Use when recording structured NDJSON telemetry.
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.
Report Exception
Tool to report an exception notice to Honeybadger. Use when sending error details (stack trace, context) for diagnostics.
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.
Upload File to S3
Tool to upload a local file to a managed S3 bucket. Use when preparing files for source-map uploads.
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.
Upload Source Map
Tool to upload JavaScript source maps for error de-minification. Use after deploying assets to Honeybadger to attach source maps.
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 Honeybadger. 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 Honeybadger.