Skip to main content

Make Waves ’26 Step into AI’s glass box. Prague, 19–20 Oct.

Register now (opens in a new tab)
Docusign
Stripe

Connect Docusign and Stripe

Explore ready-made Docusign and Stripe templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate Docusign with Stripe and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

Docusign
Trigger: [Deprecated] Watch Events
Stripe
Action: Select an action
1. Select a trigger

  • Triggers when an envelope or recipient status is changed.

  • 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.

  • Triggers when a new Agreement Manager agreement is created. Only available for Docusign IAM plans.

  • Triggers when a new document is added to a specific workspace. Only available for Docusign IAM Plans.

  • Triggers when a new user is added to a specific workspace. Only available for Docusign IAM Plans.

  • Triggers when a new workspace is created. Only available for Docusign IAM Plans.

  • 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.

  • Triggers when an existing Agreement Manager agreement is updated. Only available for Docusign IAM plans.

  • Triggers when a Workflow Builder workflow completes. Only available for Docusign IAM Plans.

  • Triggers when a Worflow Builder workflow fails. Only available for Docusign IAM Plans.

  • Triggers when a Workflow Builder workflow started. Only available for Docusign IAM Plans.

2. Select an action

  • Cancels a payment intent by its ID. For payment intents with status ’requires_capture’, the remaining capturable amount will automatically be refunded.

  • Cancels a previously created payout.

  • Capture the payment of an existing, uncaptured, charge.

  • Captures an existing uncaptured payment intent by its ID.

  • Confirms a payment intent by its ID. Upon confirmation, the payment intent will attempt to initiate a payment.

  • Creates a charge.

  • Creates a new customer object.

  • Creates a Payment Intent.

  • Creates a new payment link by line items.

  • To send funds to your own bank account, you create a new payout object.

  • Creates a new refund.

  • Creates a new invoice by the customer ID.

  • Creates a new invoice item to be added to a draft invoice.

  • Permanently deletes a customer. It cannot be undone.

  • Permanently deletes a draft invoice. Use "Void an Invoice" module for finalized invoice.

  • Permanently deletes an invoice item which is not attached to invoices, or if it’s attached to a draft invoice.

  • Finalizes a draft invoice by its ID.

  • Performs an arbitrary authorized API call.

  • Retrieves the balance transaction with the given ID.

  • Retrieves the details of a charge that has previously been created.

  • Retrieves the details of an existing customer.

  • Retrieves the details of a Payment Intent that has previously been created.

  • Retrieves the details of a payment link with the given ID.

  • Retrieves the details of an existing payout.

  • Retrieves the details of an existing refund.

  • Retrieves the details of an existing invoice with the given ID.

  • Retrieves the details of an existing invoice item with the given ID.

  • Retrieves the current account balance.

  • Updates the specified charge by setting the values of the parameters passed.

  • Updates the specified customer by setting the values of the parameters passed.

  • Updates the specified payment intent by setting the values of the parameters passed.

  • Updates a payment link by its ID.

  • Updates the specified payout by setting the values of the parameters passed.

  • Updates the specified refund by setting the values of the parameters passed.

  • Updates the specified invoice by setting the values of the parameters passed.

  • Updates the specified invoice item by setting the values of the parameters passed.

  • Voids a finalized invoice with the given ID. This cannot be undone.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between Docusign and Stripe.

[Deprecated] Watch Events
Triggers when an envelope or recipient status is changed.
Trigger
Add document to Workspace (for IAM Plans)
Adds a new document to a workspace. Only available for Docusign IAM Plans.
Action
Add to Bulk Send List
Adds a recipient to the bulk send list
Action
Add User to Workspace (for IAM Plans)
Adds a user to a workspace. Only available for Docusign IAM Plans.
Action
Bulk Send Envelope from Template
Sends envelopes based on a template to multiple recipients using a bulk send list.
Action
Cancel a Payment Intent
Cancels a payment intent by its ID. For payment intents with status ’requires_capture’, the remaining capturable amount will automatically be refunded.
Action
Cancel a Payout
Cancels a previously created payout.
Action
Cancel Workflow Instance (for IAM Plans)
Cancels a running Workflow Builder workflow instance. Only available for Docusign IAM Plans.
Action
Capture a Charge
Capture the payment of an existing, uncaptured, charge.
Action
Load more

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.

A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.

Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.

Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.