Give new code scanning alerts a report your team can act on
A new code scanning alert contains concrete findings. Notis can use the alert details in a Carbone template to create a readable report for your review and follow-up.
Trigger
New Code Scanning Alert Created
Fires when a new code scanning alert is created in a repository.
Action
Generate Carbone Report
Generates a report from a Carbone template and JSON data, and returns its render ID.
Why this helps
Security findings can be easy to postpone when their context is buried in the repository scanner, especially when a founder must turn each alert into a shareable handoff.
- Carry the alert number, rule details, tool, state, severity, and latest finding location into a report.
- Give security follow-up a consistent document format without rewriting scanner details.
- Use the configured repository, reference, tool, state, or severity filters to keep the workflow focused.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Carbone to Notis once, and prepare a Carbone template for security findings.
- 2Create the automation through the portal or in conversation, with one plain-language instruction describing which new code scanning alerts should produce a report.
- 3Choose the new code scanning alert trigger and any available alert filters; select a channel for Notis run reports.
- 4Test with a real alert and verify the generated report includes the finding details your review process needs.
Questions about this workflow
What alert information can the report use?
The trigger payload includes the alert number, rule details, scanning tool, state, severity, and location of the most recent instance.
Can this close or resolve the alert?
No. This workflow generates a Carbone report from a new alert; it does not change the GitHub alert's state.
When this happens · Trigger
Fires when a new code scanning alert is created in a repository.
Do this · Action
Generates a report from a Carbone template and JSON data, and returns its render ID.
Supported Triggers and Actions
Notis builds workflows that link GitHub to Carbone. A trigger fires from one place; an action lands in another.
GitHub triggers
Carbone actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Carbone Template
Deletes a Carbone template or version; the file is removed after a storage retention delay.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Download Template
Downloads the original template file.
New Workflow Artifact Created
Fires when a new GitHub Actions workflow artifact is created in a repository.
Generate Carbone Report
Generates a report from a Carbone template and JSON data, and returns its render ID.
Branch Changed
Fires when a branch’s commits or protection status or settings change.
Get Carbone Server Status
Checks the server’s current status and health.
New Branch Created
Fires when a new branch is created in a GitHub repository.
List Templates
Retrieves templates stored in the workspace.
Check Run Status / Conclusion Changed
Fires when a GitHub check run’s status or conclusion changes.
Set Carbone API Version
Sets the Carbone API version for subsequent requests.
Check Suite Status / Conclusion Changed
Fires when a GitHub check suite changes status or conclusion for a reference.
List Template Categories
Lists categories used to organize deployed Carbone templates.
New Code Scanning Alert Created
Fires when a new code scanning alert is created in a repository.
Upload a template
Uploads a template for document generation.
Connect any two apps with Notis in the middle.
GitHub and Carbone, or any other combination from 1,500+ 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 Carbone.