With the DocuSign eSignature integration, you can connect your DocuSign account to the BRYTER platform. This enables you to trigger the DocuSign signing process from within a BRYTER module, including for documents that are automatically generated in the module. Additionally, you can also download documents in a DocuSign envelope, check the status of an envelope, and use a DocuSign template.
Prepare your document
In the document you want to get signed, determine at which position the signatures should be inserted. To do so, add the tag <signer_1>
to your document. The signature of the first signer will be inserted at the position of this tag. Ideally, switch the color of the tag to white or whatever the background color of your document is so that the tag will be invisible in the document.
Optionally, you can add three more tags: <fullName_1>
marks the position to insert the name of the first signer from DocuSign. <title_1>
marks the position to insert the title of the first signer from DocuSign. <datesigned_1>
marks the position for the date at which the first signer signed the document. Againa, remember to change the color of the tags to make them invisible.
Then, proceed accordingly for the second signer (<signer_2>
, and so on).
Add the DocuSign integration to your module
Next, to add and configure the DocuSign integration in your module, proceed as follows:
- Select the Docusign - send-envelope integration from the Integration tab of the Action nodes.
- Add a Mail subject. This subject will be displayed in the email sent from your DocuSign account to all signers with the request for their signature
- Add a Mail body. This body will be displayed in the email sent from your DocuSign account to all signers. Ideally, you type the mail body text into a Text Block Value and reference it in the Mail body field of the Integration Action.
- In the Document(s) field, reference the document you want to get signed. It needs to be of type .docx or .pdf and should include the tags described in the section Prepare your document. You also can reference a Zip file of documents, like created by the File Upload Input node when multiple uploads are allowed.
- Add the names and the email addresses of the signers to the fields Signer 1 - Name, Signer 1 - Email, Signer 2 - Name, Signer 2 - Email, …
The output of the integration is an envelope_id. It is blank if the action was unsuccessful.
Further configurations
With the additional fields, you can optionally determine what the signing process should look like in detail.
- Supplemental document(s): Here, you can reference more documents. Those documents will not be signed. However, they will be displayed in DocuSign and need to be accepted to complete the signing process.
- Use sequential signing: By default, the email requesting a signature is send out to all signing parties simultanously. However, if you input “true” into this field, signing becomes sequential. This means, first Signer 1 gets the email requesting their signature. Only after Signer 1 signed, the next email is sent to Signer 2, requesting a signature, and so on.
- Use account defaults: If you have configured default notification settings in your DocuSign account, enter true to use them for this envelope.
- Signer 1,2,… - Title: Add the title of the signer to include it in the signed document.
- Signer 1,2,… - 2FA Telephone Number: The telephone number is used for 2-Factor-Authentication in DocuSign for this signer.
- Signer 1,2,… - 2FA Type: The type of 2-Factor-Authentication for this signer. Options relate to your installation of DocuSign.
- CC 1 - Name and CC 1 - Email: The name and email address of a person who receives a copy of the signed document via email once all parties have signed
- To enable the Docusign 2FA functionality, you first need to have this service in their DocuSign account.
- On the BRYTER side, within the Send Envelope action node, Signee’s telephone number needs to be input in this format +49XXXXXXXXXX.
- Additionally, in the “Signer - 2FA Type” field, ensure to specify “SMS” to prompt the authentication via text message. (alternatively you are able to use the “phone call” authentication too)
In case the fields Callback Correlation ID for Async Processing and Callback Module URL for Async Processing display, they are to be used for further customization by BRYTER developers and can be ignored by you.
❗Please note that once the signature process is started by the DocuSign Integration action in your module, it is from then on handled by DocuSign using your account.
Further integration node types
Download a document in an envelope
To download the documents in a DocuSign envelope that has been sent around for signatures, select a Docusign - download-documents integration from the Integration tab of the Action nodes. Then, provide the envelope ID of the envelope you want to download the documents from. Documents will be provided for download in a single file.
Get the envelope’s status
To check the latest status of the DocuSign envelope that has been sent around for signatures, select a Docusign - get-envelope-status integration from the Integration tab of the Action nodes. Then, provide the envelope ID of the envelope you want to get the status from. The status is provided by your DocuSign account and follows the DocuSign pattern.
Use DocuSign templates
You also can use DocuSign templates from within a BRYTER module. Create a Docusign - send-envelope-from-template integration from the Integration tab of the Action nodes. Select a Template that is provided by your DocuSign account and can be configured there. In the input field Template Role Prefix, you optionally can input a template roles custom prefix as Text. The default is Signer.
For the other input fields, look at the section Add the DocuSign integration to your module above. Learn more on DocuSign templates here.