Create a security awareness question from a code scanning alert
Use a new code scanning alert as a prompt for a focused secure coding question in Classmarker.
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 Question
Tool to create a new question with specified text, type, and category. Use after finalizing details. Set verify_only=True to validate without creating.
Why this helps
Security findings can be fixed without the wider team learning how to recognize or prevent the same issue.
- Turn a security finding into a reusable learning prompt.
- Help teams recognize recurring coding risks.
- Base the question on the alert details available in GitHub.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Classmarker once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3In one instruction, ask Notis to draft a secure coding question from the alert and use a specified question category.
- 4Pick New Code Scanning Alert Created as the trigger and choose where run reports go.
- 5Test with one real alert and check that the question does not assume details absent from the alert.
Questions about this workflow
Will this fix the vulnerability?
No. This workflow drafts a Classmarker question from the alert. It does not change the code or close the alert.
Can Notis include remediation guidance?
It can use guidance present in the alert details. If the alert does not contain the needed explanation, provide that context in your prompt or review the question before use.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Classmarker. A trigger fires from one place; an action lands in another.
GitHub triggers
Classmarker actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Access List Item
Tool to add one or more access codes to an access list. Use after obtaining a valid access_list_id to grant exam access.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a new question category
Tool to create a new question category. Use after confirming the parent category ID.
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 Group
Tool to create a new group. Use when you need to organize users into a specific group after planning your user structure.
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 Question
Tool to create a new question with specified text, type, and category. Use after finalizing details. Set verify_only=True to validate without creating.
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 ClassMarker User
Tool to create a new user in ClassMarker. Use after gathering user details to provision accounts. Provide user info and optional group assignments. Returns the complete API response.
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 Access List Item
Tool to delete one or more codes from an access list. Use after confirming the list exists.
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 API Key
Tool to delete an API key by its ID. Use when you need to revoke an API key immediately.
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 Group
Tool to delete a group by its ID. Use when you need to remove a group from ClassMarker.
Connect any two apps with Notis in the middle.
GitHub and Classmarker, 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 Classmarker.