Review Docmosis queue capacity before document work
A scheduled queue check gives the team a simple view of current Docmosis rendering utilization while planning Jira work.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Without a regular view of queue utilization, document-heavy work can be planned without checking current rendering capacity.
- See current queue status in a recurring run report.
- Add a capacity check to document work planning.
- Reduce manual visits to Docmosis for queue status.
Setup
Build it in a few focused steps.
- 1Connect Docmosis once in the Notis portal.
- 2Create an automation instructing Notis to retrieve the current render queue status and summarize its utilization for planning Jira document work.
- 3Pick a recurring schedule as the trigger.
- 4Choose where run reports should go.
- 5Test with one real run and review the queue status returned.
Questions about this workflow
Does this schedule or start document rendering?
No. It retrieves current queue status and utilization; it does not schedule renders.
Does the queue report identify specific Jira issues?
The queue action provides Docmosis queue status. Jira issue details or a mapping to individual issues are not provided by this action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Docmosis. A trigger fires from one place; an action lands in another.
Jira 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 Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Docmosis Environment Ready
Tool to verify environment readiness. Use when ensuring the environment is active and within quota before rendering documents.
New Project
Triggered when a new project is added in Jira
Docmosis Environment Summary
Tool to retrieve environment summary. Use when you need status, plan, and quota details of your Docmosis environment after authentication.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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.
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.
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.
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.
Jira 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.