Keep document guidance close to changing Jira work
When an issue changes, Notis can retrieve the template you name and bring its current details into the updated work context.
Trigger
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.
Action
Get Template
Tool to retrieve a single template by its id. use when you need to fetch details of a specific template before generating documents.
Why this helps
A status or assignee change can leave document planning stale, so teams may repeat searches or miss relevant guidance.
- Revisit template details when issue information changes.
- Reduce manual context switching between Jira and Documint.
- Give collaborators a timely summary to review.
Setup
Build it in a few focused steps.
- 1Connect Jira and Documint once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3In one instruction, tell Notis which template to retrieve and how to summarize it with changed issue context.
- 4Pick Jira Updated Issue as the trigger and choose where run reports go.
- 5Test with one real issue update and check that the summary is relevant.
Questions about this workflow
Do comments trigger this workflow?
No. The Updated Issue event covers changes to issue fields such as status or assignee, not comment activity.
Can this update the Documint template automatically?
This workflow retrieves template details. Updating a template is a separate available action and should be prompted only when you intend to change its settings or layout.
Which Jira issues are included?
Only updated issues in the Jira project configured for this trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Documint. A trigger fires from one place; an action lands in another.
Jira triggers
Documint actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Template
Tool to permanently delete a single template by its id. use when you need to remove an outdated or unused template; ensure the template id is correct before calling.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Template
Tool to retrieve a single template by its id. use when you need to fetch details of a specific template before generating documents.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
List Documents
Tool to list all documents in the authenticated user's account. use after obtaining a valid api key.
New Project
Triggered when a new project is added in Jira
List Templates
Tool to list all templates in the authenticated user's account. use after obtaining a valid api key.
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 Template
Tool to update a single template by its id. use when you need to modify an existing template's settings or layout after fetching its current details.
Connect any two apps with Notis in the middle.
Jira and Documint, 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 Documint.