Protect outreach from security findings
Security alerts should close loops quickly. Let Notis protect your outbound system when scanning reveals a contact that should not be emailed.
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 Contact to Blacklist
Tool to add a contact to the email blacklist. use after confirming that no further emails should be sent to a specific address. example: 'add blocked user@example.com to blacklist.'
Why this helps
A security finding can be handled in GitHub while the same address remains eligible for outreach elsewhere.
- Reduce the chance of emailing exposed or unsafe addresses
- Connect security response to outbound protection
- Remove a manual emergency step
Setup
Build it in a few focused steps.
- 1Connect GitHub and Emelia once in Notis.
- 2Create the automation by asking Notis to add any confirmed exposed contact identified by a code scanning alert to Emelia's blacklist.
- 3Select New Code Scanning Alert Created and choose the run-report channel.
- 4Test with a controlled alert or a documented example before enabling it.
Questions about this workflow
Will every alert blacklist someone?
No. Tell Notis which alert severities, tools, and confirmed contact conditions qualify.
Is this reversible?
The contact can later be removed from the blacklist with a separate action if appropriate.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Emelia. A trigger fires from one place; an action lands in another.
GitHub triggers
Emelia actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Contact to Blacklist
Tool to add a contact to the email blacklist. use after confirming that no further emails should be sent to a specific address. example: 'add blocked user@example.com to blacklist.'
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Contact To Campaign
Tool to add a contact to an email campaign. use when you have collected subscriber details and want to enroll them in a campaign.
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 Campaign
Tool to create a new email campaign. use after you have finalized the campaign name.
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.
Create LinkedIn Campaign
Tool to create a new linkedin campaign. use when you need to launch a linkedin outreach sequence.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create Webhook
Tool to create a new webhook for campaign events. use when you need to subscribe to activity updates after determining the campaign id and desired 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.
Delete Contact From Campaign
Tool to remove a contact from an email campaign. use when you need to revoke a contact's subscription from a specific campaign. note: this operation is irreversible.
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 Contact From LinkedIn Campaign
Tool to delete a contact from a linkedin campaign. use when you need to remove a contact by campaign id and contact url. call after confirming the contact exists in the 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.
Delete Webhook
Tool to delete a specific webhook. use when you need to remove an existing webhook by url after identifying the campaign.
Connect any two apps with Notis in the middle.
GitHub and Emelia, 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 Emelia.