Review your Documint document inventory on a schedule
Ask Notis to periodically list your Documint documents and prepare a short inventory report, so document follow-up does not depend on memory.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Documents
Tool to list all documents in the authenticated user's account. use after obtaining a valid api key.
Why this helps
A growing document collection can be hard to review consistently when there is no routine to surface what is in Documint.
- Create a recurring view of documents in the authenticated Documint account.
- Make document inventory review a predictable routine.
- Receive a concise report in the channel you choose.
Setup
Build it in a few focused steps.
- 1Connect 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 documents and summarize the inventory for review.
- 4Pick a recurring schedule and choose where run reports go.
- 5Test with one real run and confirm the list and summary support your review.
Questions about this workflow
Can the automation tell me which documents are outdated?
The available action lists documents. To judge whether one is outdated, provide the criteria or context in your instruction; the action alone does not establish a baseline.
Can I choose a schedule?
Yes. Select a recurring Notis schedule as the trigger when you create the automation.
Does this create or deliver PDFs?
No. The available Documint action for this workflow lists documents; it does not create or deliver PDFs.
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.