Pair job progress with document capacity
A job can finish successfully and still leave the next document step waiting; one queue check keeps that visible.
Trigger
Workflow Job State Changed
Triggers when the status, conclusion, timestamps, runner assignment, or step details of a specific GitHub Actions workflow job change between polls. The payload includes the full current job state, a list of which fields changed, and the previous status/conclusion values for easy comparison.
Action
Get Docmosis Render Queue
Tool to get current render queue status and utilization. Use when monitoring queue capacity before scheduling rendering tasks.
Why this helps
Pipeline progress is fragmented across job status and document capacity, making it hard to know what deserves attention next.
- Adds downstream capacity context to job transitions.
- Helps prioritize attention when the queue is busy.
- Reduces unnecessary reopening of workflow dashboards.
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 check Docmosis render queue utilization when a relevant workflow job changes state.
- 3Pick the Workflow Job State Changed trigger and describe the job or conclusion conditions.
- 4Choose a channel for run reports and test with one real job transition.
Questions about this workflow
Can it focus on one job?
Yes. Configure the GitHub trigger for the specific workflow job.
What does queue utilization tell me?
It shows current Docmosis render queue status and capacity pressure.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 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 Environment Ready
Tool to verify environment readiness. Use when ensuring the environment is active and within quota before rendering documents.
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 Environment Summary
Tool to retrieve environment summary. Use when you need status, plan, and quota details of your Docmosis environment after authentication.
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: 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.
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.
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.
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.
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.
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 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.
GitHub and Docmosis, 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 Docmosis.