Carry signer corrections through to Docnify
When an issue records a correction, update the recipient details on the document the correction identifies.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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 corrected email or name can sit in Linear while an outdated signer record remains in Docnify.
- Keep signer information aligned across the issue and document.
- Reduce repeated corrections and avoidable signing delays.
- Make the change traceable to the Linear update.
Setup
Build it in a few focused steps.
- 1Connect Linear and Docnify to Notis once through the portal.
- 2Create an automation conversationally or in the portal.
- 3In one prompt, ask Notis to update a recipient only when an issue update clearly identifies the document, recipient, and corrected details.
- 4Select the Linear issue-updated trigger and a report channel.
- 5Test with a real, approved correction and verify the resulting recipient details.
Questions about this workflow
Can it change any recipient on a document?
The prompt should require an exact document and recipient match. If either is unclear, it should report the ambiguity without updating.
Can it send the document after updating?
No. This action updates recipient details only.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Docnify. A trigger fires from one place; an action lands in another.
Linear 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.
Comment Received Trigger
Triggered when a comment is received.
Delete Document
Tool to delete a specific document by its ID. Use when you have confirmed the document should be permanently removed.
Issue Created Trigger
Triggered when a new issue is created.
Delete Document Field
Tool to delete a field from a document. Use when you need to remove a specific field from an existing document.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Delete document recipient
Tool to remove a recipient from a document. Use after verifying document and recipient IDs to revoke access.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Get Document
Tool to fetch a specific document by its ID. Use when you need to view a document's current state and metadata.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Get Template
Tool to fetch a specific template by its ID. Use to view a template's details and metadata.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
List Documents
Tool to list documents in the Docnify account.
Connect any two apps with Notis in the middle.
Linear 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.