Connect Docusign and Jira Cloud Platform integrations
Connect Docusign and Jira Cloud Platform with any of your favorite apps in just a few clicks. Design, build, and automate anything for your work by integrating apps like Docusign and Jira Cloud Platform to create visual automated workflows. Choose from thousands of ready-made apps or use our no-code toolkit to connect to apps not yet in our library.
Sent after a recipient accepts an elastic template.
Sent after a recipient declines an elastic template.
Triggers when one of the selected events are fired in Docusign
Triggers when an envelope has been completed.
The envelope has been completed by all the recipients.
Sent when the envelope is correctedcorrected, opens in new window within the UI or via any of the Envelopes/EnvelopesRecipients API calls.
This event is sent when an envelope is created through the DocuSign eSignature UI or when an envelope's status is set to "created" after an Envelopes:create API call.
The envelope has been declined by one of the recipients.
This event is sent after an already-sent envelope is deleted, opens in new window.
This event is sent when all recipients have opened the envelope through the DocuSign signing website. This does not signify an email delivery of an envelope.
Sent when an envelope in created or draft state is deleted or discarded within the tagging UI.
Sent when the envelope is queued to be purged, opens in new window or via the Envelopes:update API call.
Sent when the envelope is resent, opens in new window within the UI or via the Envelopes:update API call.
This event is sent when the email notification, with a link to the envelope, is sent to at least one recipient or when it is a recipient's turn to sign during embedded signing. The envelope remains in this state until all recipients have viewed the envelope.
The envelope has been voided by the sender or has expired. The void reason indicates whether the envelope was manually voided or expired.
Sent when DocuSign gets notification that an email delivery has failed. The delivery failure could be for a number of reasons, such as a bad email address or that the recipient’s email system auto-responds to the email from DocuSign.
Sent when the recipient has completed their actions for the envelope, typically (but not always) by signing.
Sent when the recipient declines to sign the document(s) in the envelope.
Sent after a Delegation rule is in place and when a delegated signer is sent an envelope within the UI or the API.
Sent when the recipient has viewed the document(s) in an envelope through the DocuSign signing web site. This does not signify an email delivery of an envelope.
Sent when the recipient selects Finish Later on an envelope.
Sent when the envelope is reassigned by a recipient within the UI.
Triggered when an envelope is resent to a recipient within the web application or using the EnvelopeRecipients : update API call.
This event is sent when an email notification is sent to the recipient signifying that it is their turn to sign an envelope.
Sent when a template is createdtemplate is created, opens in new window within the UI or via the Templates:create API call.
Sent when a template is deleted within the UI or via the recycle bin API call recycle bin API call, opens in new window.
Sent when a template is modified within the UI or via the Templates:update API call.
Adds a new attachment to a ticket.
Adds a comment to an issue.
Adds a user as a watcher to an issue.
Assigns an issue to a user.
Creates a component.
Creates a new issue.
Creates an issue link.
Creates a project version.
Creates options for a custom select field.
Deletes a Component.
Deletes an attachment.
Deletes an issue.
Deletes a commnet on a specific issue.
Deletes an issue link.
Deletes a project version.
Deletes a user as a watcher of an issue.
Deletes a custom field option.
Downloads an attachment.
Returns the details for an issue.
Returns an issue comment.
Performs an arbitrary authorized API call.
Changes the order of custom field options or cascading options in a context.
Updates a component.
Updates an existing issue.
Updates a comment to a specific issue.
Updates an issue status.
Updates a project version.
Updates the options of a custom field.
Returns a list of all the options of a select list issue field.
Retrieves changelog of an issue.
Lists current available transitions in an issue.
Returns all comments for an issue.
Returns the watchers for an issue.
Retrieves project components.
Retrieves all versions in a project.
Retrieves all users (active and inactive).
Searches for issues.
Searches for users by query.
Trusted by thousands of fast-scaling organizations around the globe
Automate your work. Build something new.
Just drag and drop apps to automate existing workflows or build new complex processes. Solve problems across all areas and teams.
Build your Docusign and Jira Cloud Platform integrations.
Create custom Docusign and Jira Cloud Platform workflows by choosing triggers, actions, and searches. A trigger is an event that launches the workflow, an action is the event.
Adds a user as a watcher to an issue.
Adds a new attachment to a ticket.
Adds a comment to an issue.
Adds a recipient to the bulk send list
Assigns an issue to a user.
Sends envelopes based on a template to multiple recipients using a bulk send list.
Creates a bulk send list
Creates options for a custom select field.
Creates a long-lived pre-filled webform link (less secure, infinite duration)
Popular Docusign and Jira Cloud Platform workflows.
Looking to get more out of Docusign and Jira Cloud Platform? With Make you can visually integrate Docusign and Jira Cloud Platform into any workflow to save time and resources — no coding required. Try any of these templates in just a few clicks.
Create JIRA issues to revoke systems access when employees are inactive in Personio
Ensure security in Personio by integrating with JIRA to promptly revoke systems access for inactive employees, effectively mitigating risks and maintaining a protected HR software environment.
TRY IT ->Send documents to sign via DocuSign from new records in Airtable
This template periodically checks for new records in Airtable and uses the retrieved information to send a document retrieved from Google Drive to sing via DocuSign. Your Airtable table should have at least these columns: 1) Name 2) Email 3) Last Modified The template is scheduled to run every 15 minutes. You can change the schedule after you set up the template.
TRY IT ->Create JIRA Cloud Platform issues from new Zendesk tickets (with attachments)
Use this template to automatically create a JIRA Cloud Platform issue when a new Zendesk ticket is created (including attachments). The attachments have to be linked to the first ticket comment. Please note that you have to disable the secure downloads option in the Zendesk tickets settings (section Attachments).
TRY IT ->Upload completed DocuSign document to Dropbox
Every time a document status is changed to Completed in DocuSign, the document will be uploaded to Dropbox.
TRY IT ->Send a document to sign via DocuSign from new form response in Typeform
Every time a new response is submitted in Typeform, a Google Drive document will be send to sign via DocuSign. This template expects your Typeform form to collect the following fields: 1. Name 2. Email
TRY IT ->Update envelope status of DocuSign document in a Google Sheets spreadsheet
This template periodically checks for documents status in DocuSign and uses the retrieved information to update the corresponding record in a Google Sheets spreadsheet. The template is using [this sample](https://docs.google.com/spreadsheets/d/17duV_jKnh8If9N4xZjQ3zLuasyUUyBy_fef5kxiD4OY/edit?usp=sharing) Google Sheets spreadsheet as a source of the data. You should make a copy of it before configuring the template. The template is scheduled to run every 15 minutes. You can change the schedule after you set up the template.
TRY IT ->Send a Slack message from DocuSign envelope status change
Every time a new event occurs in DocuSign, a Slack message will be sent immediately.
TRY IT ->Create LiquidPlanner tasks from new JIRA issues
Every time there is a new issue on JIRA Cloud Platform, Make will automatically create a new task in LiquidPlanner.
TRY IT ->Create a new ticket in Jira from a new topic in an Invision Community
This template regularly checks for new forum topics in an Invision Community and uses the retrieved information from the first post to create a new ticket in Jira. The template is scheduled to run every hour. You can change the schedule after you set up the template by clicking the clock icon on the first module but you will also need to change the filter between the modules to reflect your new schedule otherwise you will end up with the same ticket being created multiple times or no ticket created at all.
TRY IT ->
FAQ
How it works
Traditional no-code iPaaS platforms are linear and non-intuitive. Make allows you to visually create, build, and automate without limits.
Trusted by 200,000+ customers
"Make really helped us to scale our operations, take the friction out of our processes, reduce costs, and relieved our support team. It is difficult to not become a fan."
"Make drives unprecedented efficiency within our business in ways we never imagined. It’s having an extra employee (or 10) for a fraction of the cost."
"The simplicity, flexibility and ability to build real complex automations without any knowledge of programming makes it the best thing since sliced bread."
"True citizen development in the entire company. Make is present in every department, empowering the company to offer a unique customer experience."
