Create a Docuseal template from a document request issue
Turn a clearly described document request into a reusable Docuseal HTML template without restarting the brief by hand.
Trigger
New Issue Created
Triggers when a new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assignee, creator, and mentioned user. The payload includes the issue number, title, body, state, labels, assignees, comment count, creator details, timestamps, and direct links to the issue on GitHub.
Action
Create Template from HTML
Tool to create a template from html content. use when you need to define a reusable document template directly from html input.
Why this helps
Document requests in GitHub can sit in the backlog while someone has to translate the issue into a template separately.
- Starts a reusable template from a new document request.
- Keeps the source issue context in the run report.
- Applies requirements and HTML conventions you supply.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Docuseal once in the Notis portal.
- 2Create an automation in the portal or from any Notis channel.
- 3Tell Notis which new issues qualify and how to turn their requirements into HTML for a Docuseal template.
- 4Pick the New Issue Created trigger and choose where run reports should go.
- 5Test with one real issue and review the resulting template.
Questions about this workflow
Will this produce a legally reviewed agreement?
No. It creates a template from supplied requirements; have qualified reviewers validate the content before use.
What if the issue does not include enough detail?
Tell Notis to report missing requirements instead of creating a template when the issue lacks needed information.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Docuseal. A trigger fires from one place; an action lands in another.
GitHub triggers
Docuseal actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive Template
Tool to archive a specific template by its unique identifier. use after verifying the template id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Clone Template
Tool to clone an existing template by its id with a new name. use after you have the template id and desired name to duplicate it into the same or a different folder.
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.
Create Submission From PDF
Tool to create a one-off submission from a pdf file. use when you need to upload a pdf and initiate a signature workflow with optional custom field values and webhook notifications.
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.
Create Template from HTML
Tool to create a template from html content. use when you need to define a reusable document template directly from html input.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Template
Tool to retrieve details of a specific template by its unique identifier. use when you need to fetch template metadata by 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.
List Submissions
Tool to list all document submissions with optional pagination and document filtering. use when you need to retrieve and browse existing submissions.
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.
List Submitters
Tool to retrieve a list of all submitters. use when you need a roster of submitters for reporting or management.
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.
List Templates
Tool to retrieve a list of all templates. use when you need to browse available templates with optional filters before selection.
Connect any two apps with Notis in the middle.
GitHub and Docuseal, 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 Docuseal.