Get release acceptance signatures after a pull request closes
Close the loop on a shipped change by sending your prepared release acceptance document through BoldSign when a pull request closes.
Trigger
Pull Request Event
Triggered when a pull request is opened, closed, or synchronized.
Action
Send Document
Tool to send a document for eSignature. Use when you need to deliver documents to recipients for signing.
Why this helps
Release acceptance can get lost between a merged pull request and a follow-up email asking for signatures.
- Start the signing follow-up when a pull request closes.
- Keep release paperwork moving without a separate manual reminder.
- Choose which signers and prepared document Notis should use.
Setup
Build it in a few focused steps.
- 1Connect GitHub and BoldSign once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis what you want from any channel.
- 3In one instruction, name the prepared release acceptance document and the signers to receive it when a pull request closes.
- 4Pick the GitHub Pull Request Event trigger and choose where run reports should go.
- 5Test with one real closed pull request and confirm the BoldSign request.
Questions about this workflow
Does this trigger only on merged pull requests?
The listed GitHub Pull Request Event covers pull requests being opened, closed, or synchronized. State in your instruction that the document should be sent only when the pull request is closed as merged.
Do I need to provide a document and signers?
Yes. Name the prepared document and the intended signers in your instruction so Notis has the information needed for the BoldSign request.
Can Notis send different documents for different repositories?
You can describe the repository-specific rule in your instruction. Test it with a real pull request to confirm the intended document and signers are selected.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Boldsign. A trigger fires from one place; an action lands in another.
GitHub triggers
Boldsign actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Brand Details
Tool to get brand details by brand ID. Use after obtaining the brand identifier.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Brands
Tool to list all brands in the account. Use after confirming account is authenticated.
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 Custom Field
Tool to create a brand-scoped custom field. Use when you need to define and register a new custom field for a specific brand.
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.
Edit Custom Field
Tool to edit an existing custom field. Use when you need to update a custom field's properties after creation.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
List Behalf Documents
Tool to list documents sent on behalf of users. Use when fetching and filtering documents you've sent or on behalf of others.
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.
Edit Document (Beta)
Tool to edit a draft or sent document. Use when updating files, recipients, or document settings before finalizing the document.
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.
Extend Document Expiry
Tool to extend a document's expiry date. Use before signing to prolong a document's deadline.
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 Documents
Tool to list documents in My Documents with filters. Use when you need to fetch and filter documents based on various criteria.
Connect any two apps with Notis in the middle.
GitHub and Boldsign, 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 Boldsign.