DocuSign
The DocuSign integration lets you connect your DocuSign account to Harmony and automate electronic signature collection directly inside your agent workflows. Once connected, you can send documents for e-signature, track envelope status, and include signature steps as part of any larger support or operations flow - alongside other SaaS integrations like Zoom and Help Scout.
Prerequisites
Before setting up the DocuSign integration, make sure you have:
A DocuSign account with access to the templates or documents you want to use
One of the following authentication methods available:
An Integration Key and Secret Key (OAuth-based)
An RSA Key Pair for JWT authentication
Connecting DocuSign to Harmony
Harmony uses a standard OAuth-based connection flow to link your DocuSign account. No complex configuration is required to get started.
In Harmony, navigate to your integrations settings.
Select DocuSign from the list of available SaaS applications.
Follow the on-screen prompts to authenticate using your preferred method - either your Integration Key and Secret Key, or your RSA Key Pair for JWT authentication.
Once the connection is confirmed, DocuSign blocks become available in the Agent Builder.
DocuSign Blocks in the Agent Builder
After connecting your account, two DocuSign blocks are available in the Agent Builder under the Productivity category.
Send Envelope (docusign_send_envelope)
Use this block to send a document for electronic signature as part of a workflow. You can use a DocuSign template or a custom document.
Configuration options:
Document source - select a template from your DocuSign account or pass in a custom document
Recipients - configure recipients as individual employees (resolved automatically from your directory) or by entering an email address directly
Email subject - set a custom subject line for the signature request email
Fillable fields - all fillable fields from your selected template are surfaced in the workflow builder, including:
DocGen form fields - fields defined in DocuSign's document generation templates
Classic signer tabs - text fields, number fields, date fields, list dropdowns, radio buttons, and checkboxes
Select-type fields - dropdown options are fully exposed so you can pre-populate or map values
If the workflow fails mid-flight after the block has been reached, any draft envelope is automatically voided to prevent incomplete signature requests from being left open.
Check Envelope Status (docusign_check_envelope_status)
Use this block to check the current status of a previously sent envelope. This lets you build conditional logic into your workflow - for example, proceeding with an approval step only after a document has been signed.
Example Use Case
A common workflow using the DocuSign integration is an asset purchase approval flow:
An employee submits a request through the agent.
The Send Envelope block sends the relevant approval document to the designated approver for e-signature.
The Check Envelope Status block polls for completion.
The workflow continues once the document is signed, triggering any downstream steps such as provisioning or notifications.
Template Field Support
When configuring the Send Envelope block, all fillable fields from your DocuSign templates are visible in the workflow builder. This includes fields that were previously not returned by the DocuSign API. The following field types are fully supported:
DocGen form fields
Fields defined in document generation templates
Text fields
Free-text input tabs for signers
Number fields
Numeric input tabs
Date fields
Date picker tabs
List dropdowns
Dropdown selection tabs
Radio buttons
Single-selection option groups
Checkboxes
Boolean selection tabs
Select-type fields
Dropdown options surfaced for pre-population or mapping
Notes
Recipients configured as employees are resolved automatically from your Harmony directory - no need to look up or manually enter their email addresses.
The DocuSign integration works alongside other SaaS app integrations in Harmony. You can combine DocuSign blocks with actions from other connected tools in the same workflow.
Envelope voiding on workflow failure applies only to envelopes that have not yet been sent to recipients. Envelopes already delivered to signers are not affected.
Last updated
Was this helpful?
