Keep a document template aligned with Jira changes
When changing Jira work calls for a corresponding template adjustment, tell Notis exactly what to change in the Documint template you identify.
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
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.
Why this helps
Changes to project work can leave document templates out of date, and remembering to revisit them adds another follow-up task.
- Tie a template maintenance task to a relevant issue change.
- State the intended adjustment in plain language.
- Keep the change request and its trigger together for 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, identify the template and specify the exact settings or layout change Notis should make.
- 4Pick Jira Updated Issue as the trigger and choose where run reports go.
- 5Test with one real issue update and verify the template change in Documint.
Questions about this workflow
Will the workflow infer what to change from any Jira update?
No. State the template and intended change explicitly in the prompt. The trigger can fire for changes to issue fields such as status or assignee.
Does it update every template?
The available action updates a single template by its id. Identify the intended template clearly in your instructions.
Do comment edits start this workflow?
No. Jira's Updated Issue event does not fire for comment activity.
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.