Skip to content
Notis

Respond to Jira changes with the right agreement routing

When issue changes affect approval needs, have Notis add the appropriate step to the related Docusign envelope workflow.

Trigger

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.

Action

Add step to envelope workflow

This endpoint adds a new step to an existing envelope's workflow in docusign. it allows for the configuration of complex workflow rules, including delayed routing, conditional recipients, and specific actions based on envelope status or recipient actions. use this endpoint when you need to modify an envelope's workflow by adding additional steps or rules after the envelope has been created. this is particularly useful for implementing advanced routing logic or adding pauses in the signing process. the endpoint does not modify existing steps in the workflow; it only adds new ones.

Why this helps

A change in responsibility or requirements can make the existing agreement route incomplete.

  • Reflect specified issue changes in agreement routing.
  • Reduce missed approval steps after work changes.
  • Keep envelope workflows responsive to Jira context.

Setup

Build it in a few focused steps.

  • 1Connect Jira and Docusign once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name and prompt.
  • 3Tell Notis which issue changes should add a workflow step and describe the route or condition.
  • 4Pick the Jira Updated Issue trigger and choose where run reports should go.
  • 5Test with one real issue change and confirm the workflow step.

Questions about this workflow

Can it remove an old workflow step?

The listed Docusign action adds a step to an existing workflow. It does not describe removing or replacing steps.

What changes can trigger this?

The Jira event fires when an issue field changes. Describe the changes that matter and supply any criteria Jira does not expose.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Jira to Docusign. A trigger fires from one place; an action lands in another.

Jira triggers

Docusign actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add contacts to contacts list

Adds multiple contacts to a user's contacts list in docusign. this endpoint allows for bulk addition of contacts with detailed information, including cloud provider details, phone numbers, email addresses, and notary-specific information. it's particularly useful for populating a user's address book efficiently or synchronizing contacts from external sources. the endpoint supports various contact types, including regular contacts, shared contacts, and signing groups. use this when you need to add or update multiple contacts simultaneously in a docusign account. note that while it can handle a variety of contact information, it does not provide functionality for removing or deactivating contacts.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Addemailoverridestoenvelope

Adds or modifies email override settings for a specific docusign envelope, allowing customization of the reply-to email address and name, as well as bcc email addresses for archiving purposes. this endpoint should be used when you need to change email settings for an individual envelope, overriding the account-level configurations. it's particularly useful for setting up specialized archiving or customizing the reply-to information for specific envelopes. note that these changes only affect email communications that occur after the addition is made, and the bcc feature is limited to users with appropriate permissions. for security reasons, additional signer authentication is recommended when using the bcc for email archive feature.

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Add envelope attachments

Adds one or more envelope attachments to a draft or in-process envelope in docusign. this endpoint allows developers to include additional files with an envelope that are not converted to pdf and are only accessible through the api. it's useful for attaching supporting documents or metadata files that should not be part of the main signing process. the endpoint supports up to 12 attachments per envelope, with a maximum file size of 50 mb each. note that these attachments are not visible in the docusign web application and are intended for programmatic use only.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Add existing brand to group

This endpoint adds one or more existing brands to a specified group in docusign. it allows users to associate multiple brands with a group, enabling customized branding for different groups within an account. the endpoint should be used when there's a need to update the brands associated with a particular group, such as when reorganizing branding strategies or expanding brand options for specific user groups. it's important to note that this endpoint only adds existing brands to a group and does not create new brands or modify brand details.

ActionInstant

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.

TriggerInstant

Addfiletoworkspace

This endpoint adds a file to a specific folder within a docusign workspace. it allows users to upload and organize files in their docusign account, enabling better document management and collaboration. the method should be used when integrating file upload functionality with docusign workspaces, such as when adding new documents to a project or sharing files with team members. it's important to note that this endpoint only handles the file addition process and does not provide functions for file modification or deletion.

ActionInstant

Add members to signing group

This endpoint adds one or more new members to a specified signing group within a docusign account. signing groups allow multiple users to act as potential signers for a document, where any member of the group can sign on behalf of the group. this tool should be used when you need to expand or update the membership of an existing signing group. the endpoint allows you to add up to 50 members to a signing group, which is the maximum limit. when adding members, you must provide their email addresses and usernames. it's important to note that docusign recommends separating signer recipients and non-signer recipients (such as carbon copy recipients) into different signing groups to maintain clarity in the signing process.

ActionInstant

Add new users to a specified account

This endpoint adds new users to a specified docusign account, allowing bulk creation of up to 500 users in a single call. it's ideal for quickly setting up multiple users with customized permissions and settings. the endpoint requires at least a username and email for each user, but supports additional configuration options. it returns detailed information about created users, including ids and status.

ActionInstant

Addorupdateaccountstamps

This endpoint allows you to add or update one or more account stamps in a docusign account. it provides a comprehensive way to manage signature and stamp settings, including image properties, user associations, and stamp-specific details. use this endpoint when you need to create new stamps or modify existing ones for an account. it's particularly useful for bulk operations on multiple stamps. note that this endpoint doesn't handle the actual process of signing documents, but rather manages the stamps available for use in the signing process.

ActionInstant

Connect any two apps with Notis in the middle.

Jira and Docusign, 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 Docusign.