Claude Docusign connectorWhat Claude can do in your Docusign account.
The Claude Docusign connector exposes 20 tools. 14 of them read agreements, envelopes, workflows and users, 6 change something in your account, and 0 stay undocumented. Below: what Claude can look up, what it can launch, and what Docusign still labels beta.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for the team that manages agreements
Agreement data in Docusign lives across envelopes, templates and workflows. With the connector, you ask Claude where an agreement stands or which envelope is stuck, and it queries your account for you. It can also prepare an envelope or start a workflow, always from inside the conversation.
Check an agreement before a renewal call. getAllAgreements lists the agreements in your account, and getAgreementDetails opens the one you care about so Claude can summarize it.
Chase an envelope. A contract went out last week: getEnvelopes finds it by date, ID or status, listRecipients shows who has signed and which fields are filled, and updateEnvelope can void it or send a draft when needed.
Run a workflow on request. With getWorkflowTriggerRequirements Claude learns what a Workflow Builder workflow needs, then triggerWorkflow starts a new run and getWorkflowInstance follows it.
Now what the connector does not do. Docusign describes its server as a beta, with some capabilities under limited availability, and asks for a human in the loop to check the tools and the output. Its developer page also documents tools, such as sending reminders or managing brands, that are not on the directory sheet. Nothing runs by itself either: for a follow-up triggered when an envelope completes, an automation tool is the right job, and the Docusign Make integration page covers that side.
The vocabulary in one minute
Five words you will meet while plugging Docusign into Claude.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in it while answering you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs by itself; the directory lists each by name.
- Authorization
- The sign-in screen of the service itself, where you hand Claude its access. Granted once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it goes through with something that changes your account, shown right in the chat.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service.
Plug Docusign into Claude in three steps
- 01
Find Docusign in Claude
In Claude's settings, open Customize, then Connectors, and look for Docusign in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on first so each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Docusign in the window that Docusign opens itself. If the link ever breaks later on, use Disconnect and then plug it back in.
- 03
Read the authorization screen
Read the authorization screen before you accept. It belongs to Docusign, not to Claude, and it is what decides what the access covers. You can also withdraw that access later from your Docusign account.
The 20 tools, sorted by what they do
Docusign gives Claude 20 tools: 14 that read your account, 6 that change something in it.
Two groups: what Claude reads and what it changes. Tool names stay exactly as Claude shows them, in English.
- 14 read
- 6 write
What Claude reads (14)
14 toolsFourteen tools that look up agreements, envelopes, workflows and users without touching them.
getUserInfo
Returns the profile and account context of the person connected, which tells Claude which Docusign account it is working in before any other step.
getAllAgreements
Lists every agreement stored for your Docusign account, giving Claude the full inventory before it narrows down to one contract.
getAgreementDetails
Opens one specific agreement and returns its detailed information, so Claude can answer questions about that contract precisely.
getWorkflowTriggerRequirements
Retrieves what a Workflow Builder workflow needs in order to start, so Claude can gather the right inputs from you first.
getWorkflowsList
Returns the Workflow Builder workflows available in your account, which lets Claude point to the right one by name.
getWorkflowInstancesList
Lists all the runs of one given workflow, so you see how often it was used and which runs are still open.
getWorkflowInstance
Retrieves the details of a single workflow run, which is how Claude reports where a specific request is stuck.
getEnvelopes
Searches the envelopes in your account using filters such as date, ID or status code, a quick way to locate a sent document.
getEnvelope
Gets the status and metadata of a single envelope, so Claude can say whether it is sent, delivered or completed.
listRecipients
Shows the status of each recipient on an envelope along with their tab values, meaning the fields they filled in.
getTemplates
Retrieves your templates with detailed filtering, so Claude can pick the right starting document before preparing anything.
getUser
Returns detailed information about one eSignature user in the account, such as the person behind an envelope.
getUsers
Lists the eSignature users of an account, with optional filters, which gives Claude the people it can refer to.
getAccount
Retrieves detailed information about a given eSignature account, useful context when you work across several accounts.
What Claude changes (6)
6 toolsSix tools that act on envelopes or workflows. No source spells out their confirmation, so the general rule below applies.
triggerWorkflow
Approval: see the ruleStarts a new run of a Workflow Builder workflow, launching whatever steps that workflow contains in your account.
pauseNewWorkflowInstances
Approval: see the ruleStops a workflow from accepting new runs, while the question of runs already underway is left unaddressed by the source.
resumeWorkflow
Approval: see the ruleResumes a workflow that was paused, so it can accept new runs again once the problem is fixed.
cancelWorkflowInstance
Approval: see the ruleCancels one workflow run that is still in progress, ending that specific request inside Docusign.
createEnvelope
Approval: see the ruleBuilds a new envelope with documents, recipients and tabs, which is the package that goes out for signature in Docusign.
updateEnvelope
Approval: see the ruleChanges an existing envelope: Docusign lists voiding it, sending a draft and changing email details as examples.
What Claude asks before it acts
By default, Claude stops and asks you before any action it takes on an account on your behalf. The request shows up in the conversation, at the moment it matters.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked every time. They can also limit what a connector may do for the whole organization, for instance keeping reading open and closing writing. That setting applies to everyone and nobody gets around it from their own account. Finally, Claude works with your rights and nothing beyond: an envelope you cannot open in Docusign stays closed to it too.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. The answer per connector is published nowhere, and that is a real hole in the catalog rather than a gap in our reading.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each sign in. Docusign's guide adds its own condition, set against this rule in the limits section. For the live state of this one, go to Docusign's sheet in the official directory, the only place that shows it.
Where the Claude Docusign connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when an envelope is completed or a workflow finishes.
This connector is documented only by its publisher: neither Claude's help center nor Anthropic's developer docs cover it, so everything here comes from the directory sheet and Docusign's developer pages. Docusign calls the server an open beta, with some capabilities under limited availability, and says features may change. The partner badge is not a security audit, and Anthropic states on every sheet that it does not control which tools a publisher exposes. The Integrations hub gathers the automation families.
Which Claude plans can use this connector?
- Claude help center, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise an Owner has to enable each one first.
- Docusign's Claude guide for developers ↗undated, read September 2026Lists a Claude Pro account or above as a prerequisite, in a guide about adding a custom connector in Claude Desktop.
What this page followsThe two do not describe the same path: Docusign's line sits in a developer guide for a custom connector, while Anthropic's rule covers directory connectors. Neither is marked outdated. Check the directory sheet on your own account before relying on either.
Need help connecting Docusign to Claude?
A person reads every message.
