> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/integrations/saas-applications/docusign.md).

# 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 production account with access to the templates you want to use. Harmony connects to DocuSign's production environment only, so developer (demo) accounts are not supported
* A DocuSign app (integration key) with an **RSA key pair** for JWT authentication. DocuSign apps are created in a developer account, so move the app to production through DocuSign's Go-Live process first. Go-Live copies the integration key but not settings such as secrets and redirect URIs, so do the steps below in your production account

### Connecting DocuSign to Harmony

Harmony connects to DocuSign with JWT authentication: it acts as a DocuSign user you choose, using your app's integration key and RSA private key.

1. In your DocuSign production account, open **Settings** > **Apps and Keys**. Under **My Account Information**, note your **User ID**, your **API Account ID**, and your account's base URI.
2. In your app's **Actions** menu, select **Edit**, and copy the **Integration Key**.
3. In the **Service Integration** section, select **Generate RSA** and copy the private key. DocuSign shows it only once.
4. Under the redirect URIs, select **Add URI** and enter the address of your Harmony workspace without a path (for example, `https://yourcompany.harmony.io`). Then select **Save**.
5. In Harmony, navigate to **Settings** > **Integrations**, find **DocuSign** under **SaaS Applications**, and click its card.
6. Enter the **Integration Key** and the **User ID**, enter your API Account ID in **Account ID**, and paste the private key into **RSA Private Key** (it starts with `-----BEGIN RSA PRIVATE KEY-----`). In **Base URL**, select the option that matches your account's base URI.
7. Click **Connect**. A DocuSign consent window opens: sign in as the user whose **User ID** you entered and allow access.
8. Once the connection is confirmed, DocuSign blocks become available in the Agent Builder.

### DocuSign Blocks in the Agent Builder

After connecting your account, three DocuSign blocks are available in the Agent Builder under the **Productivity** category.

#### Send Document for Signing (`docusign_send_envelope`)

Use this block to send a document for electronic signature as part of a workflow, from a DocuSign template.

**Configuration options:**

* **Document source** - select a template from your DocuSign account
* **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 block fails after it has created a draft envelope (for example, while filling template fields), Harmony deletes the draft to prevent incomplete signature requests from being left open.

#### Get Envelope Status (`docusign_get_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.

#### Wait for Signature (`docusign_wait_for_envelope`)

Use this block to pause the workflow until an envelope is completed, declined, or voided. It checks every 15 minutes for the first day and hourly after that, and continues with a timed-out result if the envelope is still open when the timeout passes.

### Example Use Case

A common workflow using the DocuSign integration is an **asset purchase approval** flow:

1. An employee submits a request through the agent.
2. The **Send Document for Signing** block sends the relevant approval document to the designated approver for e-signature.
3. The **Wait for Signature** block waits until the document is signed.
4. The workflow continues once the document is signed, triggering any downstream steps such as provisioning or notifications.

### Template Field Support

When configuring the Send Document for Signing 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:

| Field Type         | Description                                             |
| ------------------ | ------------------------------------------------------- |
| 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.
* Draft cleanup on block failure applies only to envelopes that have not yet been sent to recipients. Envelopes already delivered to signers are not affected.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.harmony.io/integrations/saas-applications/docusign.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
