Route GitHub code scanning alerts to the right Doppler subscribers
When a new code scanning alert appears, keep security stakeholders in the loop without starting a separate follow-up task.
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
Add Subscriber
Tool to add a new subscriber to a specific list for a specified account.
Why this helps
Security alerts can get buried in GitHub while the people responsible for reviewing them wait for an update.
- Reduce manual alert forwarding
- Keep security contacts informed
- Preserve alert context for follow-up
Setup
Build it in a few focused steps.
- 1Connect GitHub and Doppler once in the Notis portal.
- 2Create an automation and name it for GitHub code scanning alerts.
- 3Tell Notis to add the chosen contact to the specified Doppler list when a new code scanning alert arrives, including available alert details in the run report.
- 4Pick the GitHub New Code Scanning Alert Created trigger and choose where run reports go.
- 5Test with one real alert and review the subscriber result.
Questions about this workflow
Can this workflow choose security contacts automatically?
Only if your instruction provides a clear rule and the contact details are available. Otherwise, specify the subscriber and Doppler list.
Does the alert trigger provide severity?
The event description says alerts can be filtered by severity and the payload includes alert details. Ask Notis to include available severity context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Doppler marketing automation. A trigger fires from one place; an action lands in another.
GitHub triggers
Doppler marketing automation actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Subscriber
Tool to add a new subscriber to a specific list for a specified account.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create List
Tool to create a new subscriber list for a specified account. use when you need to segment contacts into a new list.
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.
Delete List
Tool to delete a specific subscriber list by its id. use when permanently removing a list after confirming its no longer needed.
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.
Get Campaigns
Tool to retrieve all campaigns associated with the specified account. use after confirming the accountname to fetch campaigns.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get List
Tool to retrieve details of a specific subscriber list by its id. use when you need to fetch metadata of an existing list.
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.
Get Lists
Tool to retrieve all lists associated with a specified doppler account. use when you need an overview of all mailing lists. example: "retrieve lists for account partnerships@composio.dev"
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.
Get Removed Subscribers
Tool to retrieve subscribers removed from all lists. use when you need to audit unsubscribes within a date range.
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.
Get Subscriber
Tool to retrieve details of a specific subscriber by their email. use when you need to fetch subscriber information for a given account.
Connect any two apps with Notis in the middle.
GitHub and Doppler marketing automation, 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 Doppler marketing automation.