Turn Jira vendor requests into ready-to-review documents
Give each request a shareable document built from the Jira details already captured.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
Generate documents from template
Tool to generate document(s) from a template by merging JSON data or uploading a data file. Use when you need to programmatically produce one or more documents and receive metadata including a download URL.
Why this helps
Request information is often scattered across tickets and messages, slowing down review and follow-up.
- Standardize the written format for incoming requests.
- Make request context easier to share with reviewers.
- Reduce manual copying between Jira and document templates.
Setup
Build it in a few focused steps.
- 1Connect Jira and Docugenerate once in the Notis portal.
- 2Create an automation and describe the vendor request document in one instruction.
- 3Pick Jira New Issue as the trigger.
- 4Choose where run reports should go.
- 5Test with one real request issue and check the generated document.
Questions about this workflow
Does Jira need a special vendor request event?
No. This uses the listed New Issue event. It only runs for issues created in the configured project.
Can it include budget or vendor details?
Only if those details are returned by Jira or supplied separately in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Docugenerate. A trigger fires from one place; an action lands in another.
Jira triggers
Docugenerate actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Generate documents from template
Tool to generate document(s) from a template by merging JSON data or uploading a data file. Use when you need to programmatically produce one or more documents and receive metadata including a download URL.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Generate documents as ZIP
Tool to bulk generate multiple documents into a ZIP archive. Use when you need a batch of docs packaged as ZIP.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Generate document with attachments
Tool to generate a PDF with embedded attachments. Use when you need to bundle extra files into the PDF output.
New Project
Triggered when a new project is added in Jira
Generate document with merge
Tool to generate a PDF and append additional PDF files. Use when you need to merge extra pages into a generated document.
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.
Update Document
Tool to update a document's metadata. Use when renaming an existing document after confirming the document ID.
Get or list templates
Tool to retrieve or list existing templates. Use when needing template IDs and metadata before making updates or generating documents.
Update Template
Tool to update a template’s file and settings. Use after confirming the template ID and desired inputs.
Connect any two apps with Notis in the middle.
Jira and Docugenerate, 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 Docugenerate.