Give security alerts a ready remediation environment
Turn a security finding into a contained next step while the context is still fresh.
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 System
Tool to register a new system. Use when attempting to create a system via API. Note: JumpCloud does not support system creation through its REST API. Use agent installation to enroll systems.
Why this helps
Security alerts create urgency, but the isolated device or environment needed to investigate may not be prepared.
- Creates a concrete response action from each alert
- Supports safer investigation environments
- Reduces the chance that alerts sit untouched
Setup
Build it in a few focused steps.
- 1Connect GitHub and JumpCloud to Notis once.
- 2Create an automation in the portal or ask Notis to create it.
- 3Tell Notis: When a new GitHub code scanning alert appears, create a JumpCloud system record for an isolated remediation environment and summarize the alert context.
- 4Select the code-scanning-alert trigger, choose a run-report channel, and test with one alert.
Questions about this workflow
Can the alert severity be included?
Yes. Ask Notis to include the alert severity and tool details in its run report.
Does this resolve the GitHub alert?
No. It creates the JumpCloud system follow-up for investigation and remediation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Jumpcloud. A trigger fires from one place; an action lands in another.
GitHub triggers
Jumpcloud 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.
Create System
Tool to register a new system. Use when attempting to create a system via API. Note: JumpCloud does not support system creation through its REST API. Use agent installation to enroll systems.
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 Role
Tool to delete a specific JumpCloud role by its ID. Use when you need to remove a role after confirming the ID. Call only after ensuring the role is no longer assigned.
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 Jumpcloud. 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 Jumpcloud.