Claude SignWell connectorWhat Claude can do in your SignWell account.
The Claude SignWell connector exposes 14 tools: 6 read, 8 write, 0 undocumented. Claude can prepare, send and chase signature requests. Here: what stays a draft, what leaves at once, what needs your API key, and who can close it.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for whoever chases signatures
SignWell handles electronic signatures. With this connector installed in Claude Desktop, you describe the document and the signers in plain words: Claude uploads the file, prepares the request, sends it when you say so, then tells you who has signed and hands you the finished PDF. No switching between the chat and SignWell's dashboard to follow a contract.
Turn a drafted agreement into a signature request. Claude writes an NDA with you, then document_create uploads it to SignWell as a draft with its signers. Nothing reaches anyone's inbox until document_send_draft is called.
Chase the late signer. document_get reads where the document stands, and document_send_reminder emails a reminder about it, to one named recipient if you prefer.
Reuse a standard contract. template_list finds the right template, template_create_document fills in the signers and starts the signing round.
Now, what the directory sheet leaves out. That template tool sends for signature by default, while SignWell's README still says it only drafts: we explain the split below. Signature fields are placed by you in SignWell's editor, not by Claude. The connector is a desktop extension that runs on an API key, so it works in Claude Desktop only. And nothing runs on its own: no tool reacts when a document gets signed. Filing the signed PDF somewhere automatically is a job for an automation tool, a different trade; the Integrations hub covers that side.
The vocabulary, in one minute
Five words you will meet while plugging SignWell in.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude picks the ones it needs as it goes, and the directory sheet lists them by name.
- Authorization
- The step where you hand Claude the access it will use on the service. Granted once per person, and it can be taken back.
- Approval
- The confirmation Claude waits for before it goes ahead with something that changes an account, shown in the chat when it counts.
- MCP
- The shared standard behind every connector: it is what lets an assistant like Claude talk to an outside service such as SignWell.
Plug SignWell into Claude in three steps
- 01
Find SignWell in Claude Desktop
SignWell ships as a desktop extension, so open Claude Desktop. In the settings, go to Customize, then Connectors, and look for SignWell. On a Team or Enterprise workspace, an Owner or Primary Owner must switch it on before members can use it.
- 02
Start the connection
Click Connect on its row and give SignWell the access it asks for. If the link breaks later, use Disconnect, then plug the extension back in from the same row.
- 03
Mind what the access covers
SignWell's side, not Claude's, decides what the access covers, so check which SignWell account the access belongs to before relying on it. The access you grant can also be withdrawn later from the SignWell account itself.
The 14 tools, sorted by what they do
SignWell gives Claude 14 tools: 6 that read your account, 8 that change something in it.
Six tools consult your SignWell account, eight change something in it. Names stay as Claude shows them, in English.
- 6 read
- 8 write
What Claude reads (6)
6 toolsSix tools that look up documents, templates and files without touching them.
document_list
Brings back your SignWell documents, with optional filters on status, archived state or a search term, so Claude can tell you what is pending, done or stuck.
document_get
Reads the latest status of one document, so you know whether it is still out or done. SignWell also points to it as the way to confirm a dispatch went through, since the status can take a few seconds to catch up.
document_completed_pdf
Retrieves the completed PDF of a signed document, as a shareable link by default or as content Claude can display right in the chat.
template_get
Looks up one SignWell template by its ID, so Claude can check that exact template before anyone relies on it for a new request.
template_list
Lists your SignWell templates page by page, which gives Claude the catalogue to pick from when you ask for "our usual NDA" without knowing its exact title.
file_validate_text_tags
Scans a PDF for SignWell text tags, the placeholders like a signature marker typed into the document, and reports whether they will be picked up.
What Claude changes (8)
8 toolsEight tools that change something: seven act on your SignWell account, and one holds a file for upcoming requests. No source describes a confirmation of their own: the general rule further down applies.
document_create
Approval: see the ruleUploads a file to SignWell with its recipients and sets it up as a draft, always a draft, then returns the editor link where the signature fields get placed.
document_send_draft
Approval: see the ruleSends a draft that already exists, optionally adjusting some of its settings on the way; any setting left out stays as it was. Signers receive their request from that moment.
document_send_reminder
Approval: see the ruleSends a reminder email about a pending document, and can aim it at one specific recipient.
template_create
Approval: see the ruleTurns a file into a reusable SignWell template, so the same contract can be sent again without setting it up from scratch.
template_update
Approval: see the ruleUpdates an existing template, touching only the fields you want different and leaving the rest as it was.
template_delete
Approval: see the ruleRemoves a SignWell template for good. SignWell flags this tool as destructive in its own code.
template_create_document
Approval: see the ruleCreates a document from a template and, by default, sends it straight out for signing. It only stops at a draft if you explicitly ask for one.
file_store
Approval: see the ruleHolds one of your existing files, as is, for the next SignWell requests and returns a token the document and template tools accept. The file stays in memory for 60 minutes, then disappears.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before each action it takes on an account in your place. The request appears in the conversation, right when it matters.
With SignWell, that default is what stands between a request and a real email to a signer. On a Team or Enterprise workspace, owners decide whether a member can let some actions through without being asked every time. They can also cap what a connector may do for the whole organization, keeping reads and closing writes for example, and nobody overrides that from their own account. Finally, Claude works with the access of the key you provided and nothing beyond it.
Which plans it works on
Of the 819 sheets in the official directory, none displays availability plan by plan. The answer for a given connector is published nowhere.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and desktop extensions such as SignWell install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner switches a connector on for the organization before members can connect. For the current state of this one, check SignWell's sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing happens by itself when a signer opens, signs or declines.
The tool list is an observed floor, not a promise: an admin can open actions no public sheet shows. The partner badge is not a security audit, and Anthropic writes on every sheet that it neither picks a publisher's tools nor vouches for how they behave. All of this comes from SignWell's public repository, since neither Claude's help center nor Anthropic's developer docs cover it; nothing guarantees the installed extension runs that exact version. For another connector page built this way, see the Claude activecampaign connector.
Does sending from a template stop at a draft or go straight out?
- SignWell repository README ↗September 2026Out of dateBoth the document tool and the template tool always create a draft, so no email leaves until a separate send.
- Tool description in SignWell's source code ↗September 2026The template tool is ready to send and sends the document for signing by default, unless a draft is explicitly requested.
What this page followsWe follow the tool description: it is the text Claude reads when it calls the tool. Expect a document built from a template to go out for signature at once, unless you ask for a draft. The README line is outdated on this point.
Need help connecting SignWell to Claude?
A person reads every message.
