Skip to content
Notis

Turn code scanning alerts into ready-to-use document briefs

A new security alert should start a focused response, not a scavenger hunt through document templates.

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

Get Docmosis Template Structure

Tool to retrieve a template's parsed structure: fields, repeats, conditions, images, and refs. Use after uploading a template to inspect its JSON structure.

Why this helps

Security alerts create urgent context switching, and founders lose time figuring out which document template can capture the response.

  • Quickly identifies the fields and sections available for remediation documentation.
  • Keeps security follow-up anchored to the exact GitHub alert.
  • Reduces the chance of postponing documentation until the issue is forgotten.

Setup

Build it in a few focused steps.

  • 1Connect GitHub and Docmosis to Notis once through the portal.
  • 2Create an automation in the portal or ask Notis in plain language to inspect the relevant Docmosis template when a new code scanning alert appears.
  • 3Pick the GitHub New Code Scanning Alert Created trigger and tell Notis which remediation template to inspect.
  • 4Choose a channel for run reports and test it with one real alert.

Questions about this workflow

Does this resolve the security alert automatically?

No. It inspects the chosen Docmosis template and reports the structure so you can document the response faster.

Can I limit it to severe alerts?

Yes. Describe the severity condition in the plain-language automation instruction.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link GitHub to Docmosis. A trigger fires from one place; an action lands in another.

GitHub triggers

Docmosis 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.

TriggerPolling

Docmosis: Delete Image(s)

Tool to delete one or more stored images. Use when you need to remove images; ensure imageName(s) are valid before use.

ActionInstant

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.

TriggerPolling

Docmosis: Delete Template(s)

Tool to delete one or more templates from the environment. Use when you need to remove templates; multiple templates can be deleted in a single request.

ActionInstant

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

Docmosis Environment Ready

Tool to verify environment readiness. Use when ensuring the environment is active and within quota before rendering documents.

ActionInstant

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.

TriggerPolling

Docmosis Environment Summary

Tool to retrieve environment summary. Use when you need status, plan, and quota details of your Docmosis environment after authentication.

ActionInstant

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.

TriggerPolling

Docmosis: Get API Key

Tool to extract the Docmosis API access key from connection metadata. Use before other Docmosis API calls to retrieve the Bearer token from the Authorization header.

ActionInstant

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.

TriggerPolling

Get Batch Upload Status

Tool to check the status of a template batch upload job. Use when monitoring batch upload progress or checking if a batch upload has completed.

ActionInstant

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.

TriggerPolling

Download Docmosis Images

Tool to download one or more images. Use when you need to retrieve stored image files by name. If multiple names provided, images are returned in a zip archive.

ActionInstant

Commit Event

Triggered when a new commit is pushed to a repository.

TriggerInstant

Get Docmosis Render Queue

Tool to get current render queue status and utilization. Use when monitoring queue capacity before scheduling rendering tasks.

ActionInstant

Connect any two apps with Notis in the middle.

Not just GitHub and Docmosis. 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 Docmosis.