Keep Docnify signer details in sync with Jira
Record a signer correction in Jira and let Notis update the specified Docnify recipient.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
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
Signer changes can get buried in project tickets, leaving the document with outdated recipient details.
- Apply signer corrections without switching apps to find the document.
- Use a Jira issue as the request record for the change.
- Run reports show whether the update succeeded.
Setup
Build it in a few focused steps.
- 1Connect Jira and Docnify once in the Notis portal.
- 2Create an automation with a name, prompt, report channel, and trigger.
- 3In one instruction, tell Notis to use the document ID, recipient ID, and corrected signer details in the issue to update that recipient in Docnify.
- 4Pick the Jira New Issue trigger and choose where run reports go.
- 5Test with one real issue that includes verified Docnify IDs and signer details.
Questions about this workflow
What information should the Jira issue include?
Include the Docnify document ID, recipient ID, and at least one corrected recipient detail such as name, email, or role. Notis needs those values to identify and update the recipient.
Does this create a new document?
No. It updates a recipient on an existing Docnify document.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Docnify. A trigger fires from one place; an action lands in another.
Jira 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 Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Delete Document
Tool to delete a specific document by its ID. Use when you have confirmed the document should be permanently removed.
New Project
Triggered when a new project is added in Jira
Delete Document Field
Tool to delete a field from a document. Use when you need to remove a specific field from an existing document.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Delete document recipient
Tool to remove a recipient from a document. Use after verifying document and recipient IDs to revoke access.
Get Document
Tool to fetch a specific document by its ID. Use when you need to view a document's current state and metadata.
Get Template
Tool to fetch a specific template by its ID. Use to view a template's details and metadata.
List Documents
Tool to list documents in the Docnify account.
Connect any two apps with Notis in the middle.
Jira 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.