Please note that this is a premium feature which needs to be enabled by your dedicated customer success manager. For further information, please reach out to your BRYTER Customer Success Manager or firstname.lastname@example.org. Additional pricing may apply.
DocuSign offers eSignature, a way to sign electronically on different devices.
What is the DocuSign send envelope action?
Authors can use this integration node to send a DocuSign envelope for easy and electronic signing.
Why would you use the DocuSign send envelope action?
As an author, you would use this action node when your BRYTER module requires you to send out a document for signing. You can include up to eight recipients whom you want to receive e.g. a contract to electronically sign. Additionally, you can include up to eight recipients whom you want to receive the document for reference but without the option to sign.
How do you use the DocuSign send envelope action?
Once your DocuSign send envelope node is set up, you will need to input values to send a document for electronic signing. Provide a subject line, the contents of the message, as well as the actual document that needs to be signed. Under 'USE SEQUENTIAL SIGNING' determine whether you want the users to sign one by one or in a parallel manner. If sequential signing is 'true', then each email will go out after the previous recipient has signed the document. If sequential signing is turned off by entering 'false', the emails will go out at the same time and allow for parallel signing.
Further, provide values for recipients of the email. Signers require a title/honorific, name, and email. They will, as the name implies, receive the document to electronically sign. However, you can also include CC recipients, who will receive the mail but will not be allowed to sign the document.
Input and output parameters
|Mail subject||Text||Subject line for the DocuSign signing request notification|
|Mail body||Text||The message body of the DocuSign signing request notification|
|Document||File upload||The document to electronically sign|
|Use sequential signing||Text||Determines whether each signer receives the signing request notification after the previous signer has finished, or whether all signers may sign the document in parallel. If sequential signing is true, the emails will go out sequentially (first signer one, then signer two, etc.). If turned to false, the emails will go out in parallel|
|Signer 1 – title||Text||The title or honorific of the person whose signature DocuSign will request|
|Signer 1 – name||Text||The name of the person whose signature DocuSign will request|
|Signer 1 – email||Text||The recipient of the DocuSign signing request notification|
|CC 1 - name||Text||The name of someone who will receive a copy of the DocuSign signing request notification|
|CC 1 - email||Text||A CC recipient of the DocuSign signing request notification|
|This integration does not have any output parameters.
The three Signer fields are repeated for numbers 2-8, for up to eight signers.
Similarly, the two CC fields are repeated for numbers 2-8, for up to eight additional recipients.
DocuSign Anchor Tags
Anchor tags/anchor strings are placeholders placed into the document by the template author that are read by DocuSign (not BRYTER) to allow for automatic placement of the signing fields in the DocuSign signing interface.
If anchor tags are not used by the template author, each signer will be asked to place their own signing fields (such as signature, their name and signing date) in the document when signing, which may lead to user error and the document not being correctly executed.
Another benefit of using anchor tags is that, in DocuSign, the recipient has the ability to assign someone else to sign the document instead of them (for instance if they lack the authority to sign the document and need to send to their manager instead). By using the DocuSign anchor tag to populate the signer's name instead of BRYTER, if the signing is assigned to someone else DocuSign will reflect the updated signer whereas this would already be 'hard-coded' into the document if BRYTER populated this in the document.
To use an anchor tag, simple type/copy and paste the relevant tag into a document. The tag will need to be 'hidden' by changing the colour of the text to white/the document's background colour as DocuSign will not remove the tag, merely place the field over the top. Ensure to leave sufficient room/clearance around each tag (particularly the signature). Repeat for each signer, changing the number each time:
Signature Field: <signer_1>
Signer Name: <fullName_1>
Signer Title: <title_1>
Signed Date: <datesigned_1>
In order to create and access the keys described in this section you'll need to:
- Sign up for a DocuSign Sandbox (demo) Account.
- You can create and access the sandbox from the DocuSign Developer Page. Once you are inside the sandbox, you'll need to create an app under Admin > API and Keys > My apps / Integration Keys.
- As soon as you create an app, an integration key will be automatically generated.
- Go to Admin > API and Keys > My Apps / Integration Keys (click on your app) and add https://bryter.io to Redirect URIs. Remember to select the Save button.
- Have a DocuSign user with a desired email account that you plan to use only for DocuSign (see impersonated-user-guid below), because this address will receive a lot of emails from DocuSign. Therefore, avoid using any personal email address or any "official" company address. Generally, you would ask your system administrator to create and provide you with one.
💡 One BRYTER integration configuration connects a single DocuSign user account. We recommend connecting user accounts with the DS Sender and not the default DS Admin permissions set.
❗ It is very important to store your private keys somewhere since you won't be able
to access them a second time.
|authentication-server||Specifies which DocuSign environment to use, excluding the hhtps://|
|max-signers||Maximum number of signers to display; a number from 1 to 50||
|max-cc-fields||Maximum number of CC inputs to display; a number from 1 to 50||
|client-id||Also known as integration key, identifies the DocuSign integration app. Usually only one app is needed for a pair (DocuSign account, BRYTER integration).||You can find the value under
Admin > API and Keys > My Apps / Integration Keys and is the same for
the demo and production environments.
|impersonated-user-guide||Also known as API username, identifies the DocuSign user account that sends the documents to be signed||You can find the value
under Admin > Users (click on the relevant user row) > API Username.
Do not include https:// in the authentication-server value.
One BRYTER integration configuration connects a single DocuSign user account. We recommend connecting user accounts with the DS Sender and not the default DS Admin permissions set.
The private key for the integration to authenticate with DocuSign. In order to obtain the private key you need to create an RSA key pair first under Admin > API and Keys > My Apps / Integration Keys (click on your app) > Add RSA key pair.
It is very important to store your keys somewhere since you won't be able to access them a second time.
Before pasting the private key in the appropriate input field, you must replace newlines with \\n characters. A private key with replaced new lines would look like this:
-----BEGIN RSA PRIVATE KEY-----\\nMIIE...more private key content here...JlO3WKD==\\n-----END RSA PRIVATE KEY-----
Make sure the key doesn't have line breaks.