Give code scanning alerts a clear follow-up
Start a consistent, reviewable notification draft when a new code scanning alert appears in a repository.
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
Create or Update Email Template
This tool creates a new email template or updates an existing one in brevo. if a 'templateid' is provided, it performs an update; otherwise, it creates a new template.
Why this helps
Code scanning alerts compete with other work, and teams can lose time deciding how to communicate the finding and route follow-up.
- Bring alert details into a communication draft promptly.
- Use a consistent format for alert follow-up.
- Include team-specific routing and guidance supplied in your instruction.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Brevo once in the Notis portal.
- 2Create an automation in the portal or tell Notis what outcome you want from any channel.
- 3Ask Notis in one instruction to create a Brevo template from a new code scanning alert, following your supplied review process.
- 4Choose the New Code Scanning Alert Created trigger and where run reports should go.
- 5Test with one real alert and review the generated template.
Questions about this workflow
Can the workflow use alert severity?
The trigger payload includes alert details and can be filtered by severity. Ask Notis to include available severity information in the draft.
Does this fix the code issue?
No. It creates a communication template to support follow-up; investigation and remediation remain with your team.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Brevo. A trigger fires from one place; an action lands in another.
GitHub triggers
Brevo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a company
This tool allows you to create a new company in your brevo account.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create or Update Email Template
This tool creates a new email template or updates an existing one in brevo. if a 'templateid' is provided, it performs an update; otherwise, it creates a new template.
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.
Create SMS Campaign
This tool allows you to create a new sms campaign in brevo. you can specify the campaign name, sender, content, recipients (by providing list ids, exclusion list ids, or segment ids), and optionally schedule the campaign for a specific time. you can also enable unicode characters, add an organization prefix, and include unsubscribe instructions.
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.
Delete a company
Deletes a company from brevo using its unique identifier.
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 Contact
Deletes a contact from brevo using its unique identifier.
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.
Delete Email Template
This tool deletes an inactive email template from brevo. you need to provide the 'templateid' of the email template you want to delete. only inactive templates can be deleted.
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.
Delete SMS Campaign
This tool deletes an existing sms campaign.
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.
Find Contact
This tool checks if a contact exists in brevo. it searches for a contact using either an email address or mobile number, with the email being prioritized if both are provided.
Connect any two apps with Notis in the middle.
GitHub and Brevo, or any other combination from 1,000+ 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 Brevo.