Send Jira Contract Issues to BoldSign for Signature
Move contract work from Jira into a signature request without switching apps or losing track of the handoff.
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
Send Document
Tool to send a document for eSignature. Use when you need to deliver documents to recipients for signing.
Why this helps
A new contract issue can sit in Jira while someone manually prepares and sends the document for signature.
- Reduce the manual handoff between contract tracking and eSignature.
- Start a BoldSign request when a new issue arrives in the configured Jira project.
- See whether the automation ran in your selected report channel.
Setup
Build it in a few focused steps.
- 1Connect Jira and BoldSign once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3Describe the outcome: for a new Jira issue that includes the document and signer details needed, send it for signature in BoldSign and report missing details instead of guessing.
- 4Pick Jira New Issue for the configured project as the trigger.
- 5Choose a report channel, then test with one real contract issue.
Questions about this workflow
Which Jira issues start this automation?
Only new issues created in the Jira project configured for the New Issue trigger.
Can Notis send a request if signer details are missing?
Tell Notis to report the missing details rather than infer them. The prompt should specify what to do when required information is absent.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Boldsign. A trigger fires from one place; an action lands in another.
Jira triggers
Boldsign actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Brand Details
Tool to get brand details by brand ID. Use after obtaining the brand identifier.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Brands
Tool to list all brands in the account. Use after confirming account is authenticated.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Create Custom Field
Tool to create a brand-scoped custom field. Use when you need to define and register a new custom field for a specific brand.
New Project
Triggered when a new project is added in Jira
Edit Custom Field
Tool to edit an existing custom field. Use when you need to update a custom field's properties after creation.
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.
List Behalf Documents
Tool to list documents sent on behalf of users. Use when fetching and filtering documents you've sent or on behalf of others.
Edit Document (Beta)
Tool to edit a draft or sent document. Use when updating files, recipients, or document settings before finalizing the document.
Extend Document Expiry
Tool to extend a document's expiry date. Use before signing to prolong a document's deadline.
List Documents
Tool to list documents in My Documents with filters. Use when you need to fetch and filter documents based on various criteria.
Connect any two apps with Notis in the middle.
Jira and Boldsign, 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 Boldsign.