Keep the Documint template catalog visible
A recurring catalog summary gives your team a simple moment to review which templates are available in Documint.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Templates
Tool to list all templates in the authenticated user's account. use after obtaining a valid api key.
Why this helps
Templates can become hard to discover as a catalog grows, while periodic review gets pushed aside by urgent work.
- Make template review part of a predictable routine.
- See the available catalog in one report.
- Help teams find existing templates before requesting new ones.
Setup
Build it in a few focused steps.
- 1Connect Documint once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3In one instruction, ask Notis to list Documint templates and summarize the catalog for review.
- 4Pick a recurring schedule and choose where run reports go.
- 5Test with one real run and check that the summary reflects returned template information.
Questions about this workflow
Will this flag templates that are outdated?
Not by itself. It can summarize returned template information, but any definition of outdated or needed review must be provided in the prompt and supported by available details.
Does this modify templates?
No. This workflow lists templates. The available update action can modify a template when explicitly used in a separate workflow.
Can I send the summary somewhere specific?
Choose the report channel during setup.
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.