Turn Security Alerts Into Clear Next Steps
A security alert is stressful enough. Let Notis gather the document context you may need for response and follow-up.
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
Get Documents List
Tool to retrieve a list of documents associated with the account. use when you need to list all documents.
Why this helps
Security work can require policy acknowledgements or compliance records that are hard to locate under pressure.
- Bring compliance context into security response.
- Reduce frantic document searches.
- Make response work easier to delegate.
- Keep security follow-up visible until resolved.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Boloforms to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to set it up.
- 3Use this instruction: When a new GitHub code scanning alert is created, retrieve the Boloforms document list and highlight compliance or security documents relevant to the alert.
- 4Select the code-scanning-alert trigger, choose a reporting channel, and test with one alert.
Questions about this workflow
Can it prioritize severe alerts?
Yes. State that critical or high-severity alerts should receive the most prominent report.
Will it resolve the alert?
No. This workflow provides document context for your response process.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Boloforms. A trigger fires from one place; an action lands in another.
GitHub triggers
Boloforms 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.
Get Documents List
Tool to retrieve a list of documents associated with the account. use when you need to list all documents.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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.
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 Boloforms. 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 Boloforms.