Files and knowledge
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.
About Docusign eSignature
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.
Tools
What your agent can do in Docusign eSignature.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Docusign eSignature connection.
-
List envelopes
Readdocusign_list_envelopesList envelopes sent or changed since a date.
-
Get an envelope
Readdocusign_get_envelopeGet an envelope's status and its recipients.
-
List templates
Readdocusign_list_templatesList the templates in the user's account.
-
Send an envelope
Writedocusign_create_envelopeSend an envelope from a template to the named signers.
-
Download a document
Readdocusign_get_documentDownload a document from an envelope.
-
Void an envelope
Writedocusign_void_envelopeVoid an envelope that is still out for signature.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Docusign eSignature, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent send and track envelopes, and switch off
docusign_void_envelopeso 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
Connect Docusign eSignature
in three steps.
-
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.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
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.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // 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); } -
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.
run.jsConceptual exampleRun a request with the connector's tools 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);
Access
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.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Docusign eSignature connector and how to use it.
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/
This page is also available as Markdown, for agents and LLMs: /connectors/docusign-esignature.md
Guides
Use Docusign eSignature with the AI you build on.
Step-by-step setup for Docusign eSignature with a specific model, assistant or agent framework.
-
Docusign eSignature + Claude
How to connect Docusign eSignature to Claude
-
Docusign eSignature + ChatGPT
How to connect Docusign eSignature to ChatGPT
-
Docusign eSignature + Claude Code
How to connect Docusign eSignature to Claude Code
-
Docusign eSignature + Muse
How to connect Docusign eSignature to Muse
-
Docusign eSignature + Grok Bot
How to connect Docusign eSignature to Grok Bot
-
Docusign eSignature + OpenAI Dots
How to connect Docusign eSignature to OpenAI Dots
-
Docusign eSignature + Claude Duet
How to connect Docusign eSignature to Claude Duet
-
Docusign eSignature + Hermes Agent
How to connect Docusign eSignature to Hermes Agent
-
Docusign eSignature + OpenClaw
How to connect Docusign eSignature to OpenClaw
FAQ
Docusign eSignature and Agent200, answered.
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.