Make Security Alerts Visible in ServiceM8
Important alerts should become visible work, not another tab to remember.
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
ServiceM8 Create Job Note
Tool to create a new job note in servicem8. use when you need to attach additional information to a specific job after obtaining its uuid.
Why this helps
Security findings can be acknowledged in GitHub but forgotten during customer or maintenance work.
- Makes security follow-up visible to operations
- Reduces missed remediation context
- Supports a consistent response to important findings
Setup
Build it in a few focused steps.
- 1Connect GitHub and ServiceM8 to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it.
- 3In one instruction, tell Notis which code scanning alerts should be added to the related ServiceM8 job as notes.
- 4Pick the new code scanning alert trigger and choose the reporting channel.
- 5Test with one alert in a controlled repository.
Questions about this workflow
Can alerts be limited by severity?
Yes. State the severity or scanning tool to include in the instruction.
Is this a security system of record?
No. It adds operational context in ServiceM8 while GitHub remains the alert source.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Servicem8. A trigger fires from one place; an action lands in another.
GitHub triggers
Servicem8 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.
ServiceM8 Create Job Note
Tool to create a new job note in servicem8. use when you need to attach additional information to a specific job after obtaining its uuid.
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.
ServiceM8 Create Job Payment
Tool to create a new job payment in servicem8. use when you have collected payment details and need to record payment against a job. example: "create a 100.00 cash payment for job 123e4567-e89b-12d3-a456-426614174000 at 2023-01-01 13:00:00."
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 a new Job
Tool to create a new job in servicem8. use when you have gathered all job details and need to push a record. example: "create a quote job for 123 main st with po #1234."
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 Job Note
Tool to delete a specific job note. use when you need to archive a note by its uuid.
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.
ServiceM8 Delete Job Payment
Tool to delete (archive) a specific job payment by its uuid. use when you need to archive a payment record.
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.
List All Assets
Tool to list all servicem8 assets. use when you need a comprehensive asset registry, including custom fields, for inventory or reporting.
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.
List All Clients
Tool to list all servicem8 clients. use when you need a complete set of customer records for integrations or reporting.
Commit Event
Triggered when a new commit is pushed to a repository.
List All Document Templates
Tool to list document templates. use when you need to retrieve available template uuids and names before generating job documents.
Connect any two apps with Notis in the middle.
Not just GitHub and Servicem8. 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 Servicem8.