Add requested signers to Docnify from Jira
Capture a signing request in Jira, then add its specified recipient to the matching Docnify document.
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
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.
Why this helps
A signing request can sit in a ticket while someone separately tracks down the right document and enters recipient details.
- Turn a ticketed request into a recipient addition.
- Keep recipient details with the Jira request.
- Reduce manual re-entry across apps.
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 add the requested recipient to the Docnify document identified in the issue, using the supplied name, email, and any signing order or authentication options.
- 4Pick the Jira New Issue trigger and choose where run reports go.
- 5Test with one real issue containing a verified document ID and recipient details.
Questions about this workflow
Can Notis add a signer if the issue has no document ID?
The issue needs to identify the Docnify document. Include its ID along with recipient details so Notis can target the intended document.
Can the issue specify signing order?
Yes, the action supports an optional signing order and authentication options. Include the intended values in the issue if they are needed.
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.