# Docusign eSignature for AI agents. Managed auth, ready-made tools.

> Send documents for signature, track envelopes and download signed copies in Docusign on behalf of each of your users.

- Page: https://www.agent200.com/connectors/docusign-esignature/
- Category: Files and knowledge
- Authentication: Managed OAuth
- Identifier in code: `docusign_esignature`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-18

## Instructions for AI agents

Connector: Docusign eSignature, through Agent200. In code: "docusign_esignature".
What it does: Send documents for signature, track envelopes and download signed copies in Docusign on behalf of each of your users.
Page: https://www.agent200.com/connectors/docusign-esignature/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Docusign eSignature's own page, through the authorization link Agent200 returns. Never ask a user for a Docusign eSignature password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: docusign_list_envelopes, docusign_get_envelope, docusign_list_templates, docusign_get_document. Write tools: docusign_create_envelope, docusign_void_envelope. Name "docusign_esignature" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/docusign-esignature/framework/claude/
   https://www.agent200.com/connectors/docusign-esignature/framework/chatgpt/
   https://www.agent200.com/connectors/docusign-esignature/framework/claude-code/
   https://www.agent200.com/connectors/docusign-esignature/framework/muse/
   https://www.agent200.com/connectors/docusign-esignature/framework/grok-bot/
   https://www.agent200.com/connectors/docusign-esignature/framework/openai-dots/
   https://www.agent200.com/connectors/docusign-esignature/framework/claude-duet/
   https://www.agent200.com/connectors/docusign-esignature/framework/hermes-agent/
   https://www.agent200.com/connectors/docusign-esignature/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

## About

With the Docusign eSignature connector, your agent works in each user's own Docusign account. It can send an envelope from a template, check who has signed, download the completed documents and void an envelope, using only the tools your project allows.

Docusign eSignature is Docusign's service for sending documents for electronic signature.

## Docusign eSignature tools

- **List envelopes** (`docusign_list_envelopes`, read): List envelopes sent or changed since a date.
- **Get an envelope** (`docusign_get_envelope`, read): Get an envelope's status and its recipients.
- **List templates** (`docusign_list_templates`, read): List the templates in the user's account.
- **Send an envelope** (`docusign_create_envelope`, write): Send an envelope from a template to the named signers.
- **Download a document** (`docusign_get_document`, read): Download a document from an envelope.
- **Void an envelope** (`docusign_void_envelope`, write): Void an envelope that is still out for signature.

## Limits you can set

**Turn single tools on or off.** Let the agent send and track envelopes, and switch off `docusign_void_envelope` so it can never cancel one.

**Restrict what the agent reaches.** Choose the endpoints and scopes a project may use, for example reading envelope status but not sending. A call outside them is refused.

## Get started

### Step 1: Set up the SDK

Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Let your user connect Docusign eSignature

Each end user authorizes their own Docusign eSignature account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

File `connect.js`:

```js
// Each end user authorizes their own Docusign eSignature account, once.
const connection = await agent200
  .user("user_123")
  .connect("docusign_esignature");

if (connection.authorizationUrl) {
  // Show this link to your user; Agent200 handles the rest.
  console.log(connection.authorizationUrl);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 3: Run with the Docusign eSignature tools

Name the user, the model and the tools. The model decides which Docusign eSignature tools to call, and Agent200 executes them with that user's connection.

File `run.js`:

```js
const result = await agent200
  .user("user_123")
  .run({
    model: "openai/gpt-5.6-sol",
    input: "Has the Acme contract been signed yet",
    tools: ["docusign_esignature"],
  });

console.log(result.output);
```

(Conceptual example of the Agent200 SDK.)

## Sign-in and permissions

**Who signs in.** Each of your users, once, on Docusign's own sign-in page. You never see or store their Docusign password.

**What access is requested.** The scopes the connection needs, such as sending and reading envelopes, listed on Docusign's authorization screen. Users can remove the app later from their Docusign account settings.

## Example requests

- "Has the Acme contract been signed yet"
- "Send the NDA template to jamie@example.com"
- "Download the signed offer letter for Sam"

## Guides: Docusign eSignature with your AI framework

- [Docusign eSignature + Claude](https://www.agent200.com/connectors/docusign-esignature/framework/claude.md): Set up DocuSign eSignature for Claude with Agent200, then check which tools are available to your agent.
- [Docusign eSignature + ChatGPT](https://www.agent200.com/connectors/docusign-esignature/framework/chatgpt.md): Set up DocuSign eSignature for ChatGPT with Agent200, then check which tools are available to your agent.
- [Docusign eSignature + Claude Code](https://www.agent200.com/connectors/docusign-esignature/framework/claude-code.md): Set up DocuSign eSignature for Claude Code with Agent200, then check which tools are available to your agent.
- [Docusign eSignature + Muse](https://www.agent200.com/connectors/docusign-esignature/framework/muse.md): Set up DocuSign eSignature for Muse with Agent200, then check which tools are available to your agent.
- [Docusign eSignature + Grok Bot](https://www.agent200.com/connectors/docusign-esignature/framework/grok-bot.md): Set up DocuSign eSignature for Grok Bot with Agent200, then check which tools are available to your agent.
- [Docusign eSignature + OpenAI Dots](https://www.agent200.com/connectors/docusign-esignature/framework/openai-dots.md): Set up DocuSign eSignature for OpenAI Dots with Agent200, then check which tools are available to your agent.
- [Docusign eSignature + Claude Duet](https://www.agent200.com/connectors/docusign-esignature/framework/claude-duet.md): Set up DocuSign eSignature for Claude Duet with Agent200, then check which tools are available to your agent.
- [Docusign eSignature + Hermes Agent](https://www.agent200.com/connectors/docusign-esignature/framework/hermes-agent.md): Set up DocuSign eSignature for Hermes Agent with Agent200, then check which tools are available to your agent.
- [Docusign eSignature + OpenClaw](https://www.agent200.com/connectors/docusign-esignature/framework/openclaw.md): Set up DocuSign eSignature for OpenClaw with Agent200, then check which tools are available to your agent.

## FAQ

### Who handles the Docusign eSignature OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Docusign eSignature.

### Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Docusign eSignature connection, never another user's. It cannot reach anything the user or Docusign eSignature has not authorized.

### Can I limit what my agent can do in Docusign eSignature?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

## Related connectors

- [Google Drive](https://www.agent200.com/connectors/google-drive.md): Find, read and organize the files in each user's Drive.
- [OneDrive](https://www.agent200.com/connectors/onedrive.md): Search, read, upload and share OneDrive files, including Word, Excel and PowerPoint documents, on behalf of each of your users.
- [Dropbox](https://www.agent200.com/connectors/dropbox.md): Search, read, upload and organize Dropbox files, and create shared links, on behalf of each of your users.
- [Notion](https://www.agent200.com/connectors/notion.md): Search, read and write Notion pages and databases on behalf of each of your users.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
