Find the Related BoldSign Document from a New Jira Issue
Give new contract issues a fast check for an existing signature document, with unmatched items easy to spot.
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
List Documents
Tool to list documents in My Documents with filters. Use when you need to fetch and filter documents based on various criteria.
Why this helps
Teams can lose time searching BoldSign manually to find the document referenced by a new Jira issue.
- Cut down on manual searches across Jira and BoldSign.
- Use available issue details to identify relevant documents.
- Make missing or ambiguous matches visible for a person to resolve.
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: search BoldSign documents for a match to each new Jira issue, summarize the best match and report when the result is missing or ambiguous.
- 4Pick Jira New Issue for the configured project as the trigger.
- 5Choose a report channel, then test with one real issue that references a document.
Questions about this workflow
Does the automation create a document if it cannot find one?
No. This workflow searches existing BoldSign documents and reports when it finds no suitable match.
What makes a reliable match?
A shared document name, contract reference, or other identifier present in the Jira issue and BoldSign results. Tell Notis which available detail to prioritize.
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.