Keep release documents current as details change
When release notes or publication details change, create a fresh document from the current release information Notis receives.
Trigger
GitHub Release State Changed
Triggers when a specific GitHub release (identified by tag name) changes. Monitors the release title, body/notes, draft flag, prerelease flag, published timestamp, target branch/commit, and the set of attached assets. The payload includes the full current release details, a list of which fields changed, and the previous values for comparison.
Action
Generate documents from template
Tool to generate document(s) from a template by merging JSON data or uploading a data file. Use when you need to programmatically produce one or more documents and receive metadata including a download URL.
Why this helps
Release details can change late in the process, leaving previously prepared documents out of date.
- Generate a document from updated release details.
- Make release changes easier to follow up on.
- Use a consistent release document template.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Docugenerate once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis from any channel.
- 3In one instruction, describe the release document to generate from the current details Notis receives.
- 4Pick GitHub Release State Changed as the trigger and choose where run reports go.
- 5Test with one real release change and confirm the document reflects the available current details.
Questions about this workflow
Does the trigger include the full release notes?
The event description includes release body or notes among the monitored fields and current release details. Ask Notis to use the data it receives; check your test run to confirm the content available.
Will this edit the existing release document?
The selected action generates documents from a template. It does not update an existing generated document, so each qualifying change can create a new document.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Docugenerate. A trigger fires from one place; an action lands in another.
GitHub triggers
Docugenerate actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Generate documents from template
Tool to generate document(s) from a template by merging JSON data or uploading a data file. Use when you need to programmatically produce one or more documents and receive metadata including a download URL.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Generate documents as ZIP
Tool to bulk generate multiple documents into a ZIP archive. Use when you need a batch of docs packaged as ZIP.
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.
Generate document with attachments
Tool to generate a PDF with embedded attachments. Use when you need to bundle extra files into the PDF output.
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.
Generate document with merge
Tool to generate a PDF and append additional PDF files. Use when you need to merge extra pages into a generated document.
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 Document
Tool to update a document's metadata. Use when renaming an existing document after confirming the document ID.
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.
Get or list templates
Tool to retrieve or list existing templates. Use when needing template IDs and metadata before making updates or generating documents.
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.
Update Template
Tool to update a template’s file and settings. Use after confirming the template ID and desired inputs.
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 Docugenerate, 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 Docugenerate.