Recheck document timing when the project date moves
A changed target date can prompt a fresh look at the agreement connected to the project.
Trigger
Project Properties Updated
Fires when properties on a Linear project change (status, lead, target date, priority, etc.). Covers projects in both public and private teams — polls 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
A moved delivery date can make an existing signing timeline stale without creating an obvious reminder to check it.
- Prompt a review when project timing shifts.
- Keep agreement details close to delivery planning.
- Avoid relying on memory to revisit document timelines.
Setup
Build it in a few focused steps.
- 1Connect Linear and Docnify to Notis once through the portal.
- 2Create an automation through the portal or by asking Notis.
- 3Write one prompt asking Notis to fetch the project-referenced Docnify document when the target date changes and report its current details.
- 4Select the Linear project-properties-updated trigger and a channel for reports.
- 5Test with a project whose document reference is clear.
Questions about this workflow
Does this change a signing deadline?
No. It fetches the document details for review and does not edit the document.
How does it know which project change was a date change?
Describe the relevant date change in the plain-language prompt and test that behavior with a real project update.
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.