Route customer security notices from GitHub alerts
Use a new code scanning alert as a prompt for a carefully scoped customer notice through the Customer.io broadcast you specify.
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
Trigger Broadcast
Tool to manually trigger a broadcast. use when you need to override the default audience and provide personalization data after confirming the broadcast id.
Why this helps
When an alert has customer impact, preparing and sending a clear notice can compete with the work of investigating it.
- Bring alert context into the customer communication step.
- State the conditions for customer notification in plain language.
- Keep the broadcast decision tied to your team's defined criteria.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Customer.io once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis from any channel.
- 3In one instruction, specify which alerts warrant a customer notice, the approved message approach, and the Customer.io broadcast to trigger.
- 4Pick New Code Scanning Alert Created as the trigger and choose where run reports go.
- 5Test with one real alert and confirm the result is appropriate.
Questions about this workflow
Will every code scanning alert notify customers?
Your instruction should define which alerts qualify, using details available in the event such as severity, state, tool, or Git reference. Do not assume an alert proves customer impact.
Can Notis determine which customers are affected?
Only if the relevant customer or product mapping is available to Notis or supplied in your instruction. The GitHub alert event does not itself establish which customers are affected.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Customerio. A trigger fires from one place; an action lands in another.
GitHub triggers
Customerio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Suppress Customer Profile
Tool to suppress a person. use when you need to permanently delete a customer's profile and prevent them from being re-added.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Integrations
Tool to retrieve a list of integrations in your workspace. use when you need to discover configured integrations.
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 Messages
Tool to retrieve a list of messages sent from your workspace. use when you need paginated delivery metrics for messages, e.g., list email messages delivered between two timestamps.
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 Segment Details
Tool to retrieve details of a specific segment. use after identifying the segment id from list segments.
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 Segment Membership
Tool to retrieve people in a specific segment. use when you need to page through segment membership after identifying segment id.
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 Segments
Tool to retrieve a list of segments in your workspace. use when you need to fetch all segments after configuring segment rules.
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 Trigger
Tool to retrieve details about a specific trigger. use after triggering a broadcast to confirm its status and metadata.
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 Triggers
Tool to retrieve a list of triggers for a specific broadcast. use after identifying broadcast id to inspect associated triggers.
Connect any two apps with Notis in the middle.
GitHub and Customerio, 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 Customerio.