Close the loop between review feedback and documents
Review feedback is easier to finish when the supporting document structure is still visible.
Trigger
Pull Request Review Submitted
Triggers when a new review is submitted for a GitHub pull request. Emits an event for each newly submitted review on the monitored pull request, covering all review types: APPROVED, CHANGES_REQUESTED, COMMENTED, and DISMISSED.
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
After a review, founders may address code comments but lose track of the release or change documentation that belongs with the update.
- Keeps documentation visible at a natural review checkpoint.
- Helps contributors understand the expected change-record shape.
- Reduces incomplete handoffs after approval or requested changes.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Docmosis to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to inspect the change-log template whenever a pull request review is submitted.
- 3Pick the Pull Request Review Submitted trigger and describe which review outcomes should be included.
- 4Choose a reporting channel and test with one real review.
Questions about this workflow
Can it distinguish approvals from requested changes?
Yes. State which review types should trigger the automation.
Does it summarize the review?
The defined action checks the Docmosis template structure; any summary should be requested in the instruction if supported.
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.
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.
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.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Docmosis Environment Ready
Tool to verify environment readiness. Use when ensuring the environment is active and within quota before rendering documents.
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.
Docmosis Environment Summary
Tool to retrieve environment summary. Use when you need status, plan, and quota details of your Docmosis environment after authentication.
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.
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.
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.
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.
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.
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.
Commit Event
Triggered when a new commit is pushed to a repository.
Get Docmosis Render Queue
Tool to get current render queue status and utilization. Use when monitoring queue capacity before scheduling rendering tasks.
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.