Keep private-team signing updates grounded in document details
Check the referenced agreement when a private team shares a signing update in Linear.
Trigger
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).
Action
Get Document
Tool to fetch a specific document by its ID. Use when you need to view a document's current state and metadata.
Why this helps
Sensitive internal work can still require repeated status checks when document updates are buried in a private issue thread.
- Bring current document details into an internal follow-up.
- Keep private-team agreement checks tied to the relevant discussion.
- Reduce manual back-and-forth between tools.
Setup
Build it in a few focused steps.
- 1Connect Linear and Docnify to Notis once through the portal.
- 2Create an automation by asking Notis in plain language or using the portal.
- 3Prompt Notis to fetch the Docnify document identified in a private-team signing comment and report its current details without modifying it.
- 4Select the private-team comment trigger and a report channel appropriate for the work.
- 5Test with a real private-team comment and confirmed document reference.
Questions about this workflow
Does this cover public-team comments too?
No. It uses the private-team comment trigger. Public-team comments have a separate Linear event.
Will it expose private issue content elsewhere?
Run reports go to the channel selected for the automation, so choose a channel suitable for the issue context.
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.