Keep signer details current when a pull request changes
When a pull request change affects the signing contact, update the recipient details on the identified Docnify document.
Trigger
Pull Request State / Properties Changed
Triggers when a specific GitHub pull request changes any of these tracked properties: state (open/closed), title, body, draft status, lock status, merge status, assignees, labels, requested reviewers, or milestone. The payload includes the full current PR details, the list of changed field names, and their previous values.
Action
Update Document Recipient
Tool to update a recipient's details (name, email, role) on a document. Use after confirming document and recipient IDs. Provide at least one field to update.
Why this helps
A changed owner or reviewer can leave signing details out of date if document contacts are maintained separately.
- Tie a recipient update to a monitored pull request change.
- Keep the target document and recipient explicit in the instruction.
- Update only the signer details supplied for the change.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Docnify once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3Describe the outcome in one instruction, providing the confirmed document ID, recipient ID, and details to update.
- 4Pick Pull Request State / Properties Changed as the trigger and choose where run reports go.
- 5Test with one real pull request property change and verify the intended recipient details were updated.
Questions about this workflow
Can the workflow infer a signer's email from a GitHub reviewer?
Do not assume that GitHub provides the email needed by Docnify. Supply the recipient details in the instruction or another available source.
What is needed before updating a recipient?
The action requires the document and recipient IDs, plus at least one recipient field to update.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Docnify. A trigger fires from one place; an action lands in another.
GitHub triggers
Docnify actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Document Recipient
Tool to add a recipient to a document. Use after confirming the document's ID. Optionally specify signing order and authentication options.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Document Fields
Tool to create one or more fields on a document. Use after fetching a document to add fields before sending.
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.
Delete Document
Tool to delete a specific document by its ID. Use when you have confirmed the document should be permanently removed.
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.
Delete Document Field
Tool to delete a field from a document. Use when you need to remove a specific field from an existing 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.
Delete document recipient
Tool to remove a recipient from a document. Use after verifying document and recipient IDs to revoke access.
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 Document
Tool to fetch a specific document by its ID. Use when you need to view a document's current state and metadata.
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.
Get Template
Tool to fetch a specific template by its ID. Use to view a template's details and metadata.
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 the Docnify account.
Connect any two apps with Notis in the middle.
GitHub and Docnify, 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 Docnify.