See the Documint template inventory during a document related pull request
When a monitored pull request receives a commit, ask Notis to list your Documint templates and summarize the inventory alongside the pull request context.
Trigger
New Commit Added to Pull Request
Triggers when a new commit is pushed to a specific pull request. Monitors all commits on the specified pull request and emits an event for each newly added commit. This covers force-pushes and additional commits pushed to the PR's head branch.
Action
List Templates
Tool to list all templates in the authenticated user's account. use after obtaining a valid api key.
Why this helps
Document-related code changes can move through review without anyone checking which templates exist or may need a coordinated update.
- Bring the current Documint template inventory into a pull request workflow.
- Keep template review visible as new commits arrive.
- Help reviewers identify templates that may need separate follow-up.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Documint once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis from any channel.
- 3In one instruction, ask Notis to list Documint templates and summarize the inventory with the monitored pull request context.
- 4Pick New Commit Added to Pull Request and choose where run reports go.
- 5Test with one real pull request commit and check that the inventory is useful to reviewers.
Questions about this workflow
Does this identify the exact template affected by a code change?
Not automatically. Notis can summarize the pull request context and template inventory, but the affected template must be identified in your instruction or by a person reviewing the report.
Does the workflow change templates?
No. Its Documint action lists templates so the report can support review and follow-up.
Will it run for every repository pull request?
The listed trigger monitors a specific pull request, so choose the pull request that should prompt this inventory check.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Documint. A trigger fires from one place; an action lands in another.
GitHub 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 Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
List Documents
Tool to list all documents in the authenticated user's account. use after obtaining a valid api key.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
List Templates
Tool to list all templates in the authenticated user's account. use after obtaining a valid api key.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Connect any two apps with Notis in the middle.
GitHub 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.