Keep your team informed about code scanning alerts
When GitHub finds a new code scanning issue, send a ChMeetings notification with the alert details and repository link.
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
ChMeetings: Send Notification
Tool to attempt sending a notification.
Why this helps
Security findings can sit unnoticed when developers and the people coordinating a response work in different tools.
- Bring new findings to the team's attention sooner.
- Include the repository and alert details to reduce lookup time.
- Keep a response team informed without manually forwarding alerts.
Setup
Build it in a few focused steps.
- 1Connect GitHub and ChMeetings once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe the notification you want Notis to send in one plain language instruction.
- 4Pick the GitHub New Code Scanning Alert Created trigger and choose where run reports go.
- 5Test with one real alert and confirm the notification contains useful context.
Questions about this workflow
Can I limit this to a specific severity?
The trigger supports severity filters. Choose the relevant alert scope when selecting the GitHub trigger.
What information can the notification include?
Ask Notis to summarize the alert details returned by GitHub and include the repository context or available link.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Chmeetings. A trigger fires from one place; an action lands in another.
GitHub triggers
Chmeetings actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Invite Meeting Attendee
Tool to invite a new attendee to a specified meeting. Use when you need to add attendees before the meeting begins.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Attendee Details
Tool to retrieve details for a specific attendee. Use when you have an attendee_id and need the attendee's full profile.
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.
ChMeetings: Create Meeting
Tool to create a new meeting in ChMeetings. Use when you have all meeting details and need to schedule it via the ChMeetings API.
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.
ChMeetings: Create Organization
Tool to create a new organization.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
ChMeetings: Create Reminder
Tool to create/schedule a reminder for a meeting in ChMeetings.
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 Meeting Attendee
Tool to remove an attendee from a meeting. Use after confirming attendee details.
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.
List Meeting Attendees
Tool to list attendees of a meeting. Use when you need to retrieve attendees for a specific meeting.
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.
ChMeetings: Delete Meeting
Tool to delete an existing meeting. Use when you have confirmed the meeting ID to permanently remove the meeting.
Connect any two apps with Notis in the middle.
GitHub and Chmeetings, 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 Chmeetings.