Claude SignNow connectorWhat Claude can do in your SignNow account.
The Claude SignNow connector exposes 16 tools. 6 read your documents, templates and invite statuses, 6 create or send something, and 4 are listed without any description. Below: what Claude can send for signature, what it checks, and where the sources stop.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when signatures run through Claude
Chasing a signature usually means opening SignNow, finding the document, checking who is still pending and sending it again. With the connector, you describe what you need and Claude handles the SignNow side: pick a template, prepare the document, send the invite, then tell you where things stand. SignNow's own documentation adds that the assistant typically has you preview the document and confirm recipients before an invite goes out.
Send a contract from a template. An office manager needs the standard NDA sent to a new contractor. Claude looks it up with list_all_templates, turns it into a document with create_from_template, fills the text fields through update_document_fields and sends it with send_invite.
Know who has not signed. Before a Friday deadline, get_invite_status returns the current steps of an invite, so you see which signer is still holding things up.
Hand over the signed file. Once everyone has signed, get_document_download_link gives you a direct link to the file, or the merged output for a group of documents.
What it will not do: text fields are the only ones it can pre-fill, and four template variants listed in the directory are described nowhere. Nothing runs by itself either: no tool reacts when a document gets signed. To file each signed contract somewhere automatically, a scenario tool fits better, and the SignNow Make integration page covers that side. They do different jobs.
The vocabulary in one minute
Five words you will meet while plugging SignNow into Claude.
- 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 action the connector opens to Claude. Claude picks the ones it needs by itself; the directory lists them by name.
- Authorization
- The sign-in screen of SignNow itself, where you hand Claude the access it will use. Given once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it finishes something that changes your account, shown right in the conversation.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as SignNow.
Connect SignNow to Claude in three steps
- 01
Find SignNow in Claude
In Claude's settings, open Customize, then Connectors, and look for SignNow in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before each member can sign in.
- 02
Start the connection
Click Connect on its row and sign in to SignNow in the window the service opens itself. If the link breaks one day, use Disconnect, then plug it back in from the same row.
- 03
Read the authorization screen
Read the service's screen before you accept. It belongs to SignNow, not Claude, and it decides what the access covers. You can also withdraw that access later from your SignNow account.
The 16 tools, grouped by what they do
SignNow gives Claude 16 tools: 6 that read your account, 6 that change something in it, and 4 no official source describes.
Three groups: what Claude reads, what it creates or sends, and what no official source describes. Names stay in English, as Claude shows them.
- 6 read
- 6 write
- 4 not documented
What Claude reads (6)
6 toolsSix tools that look at documents, templates and invites without changing them.
list_all_templates
Returns your templates and template groups with a light set of details, 50 per page by default. It is how Claude finds the right starting point before building a document.
list_documents
Browses your documents and document groups with their status, and can filter them: signed, pending, waiting for you, waiting for others, or not yet sent.
get_invite_status
Tells Claude where a given invite stands, step by step, for a single document or a group. You learn who signed and who is still pending.
get_document_download_link
Produces a direct download link for a document; for a group, the link points to the merged output. You get the file itself, not a summary of it.
get_signing_link
Fetches the link to sign a document or group that is already waiting for your own signature, so you can sign straight away.
get_document
Gives Claude the structure of a document or group, with the values already entered in its fields. Handy for checking what is filled in before anything goes out.
What Claude creates or sends (6)
6 toolsSix tools that act on your SignNow account. No Anthropic source describes a confirmation specific to them: the general rule below applies.
send_invite
Approval: see the ruleEmails signature invites for a document or a group, with signers in a set order if you need one. SignNow describes it as built for confirmed sends: the assistant typically shows you a preview and checks recipients first.
create_embedded_invite
Approval: see the ruleOpens a signing session without sending any email, for a document, a group or a template. With a template, it creates the document first.
create_embedded_sending
Approval: see the ruleSets up an embedded sending and management screen for a document, group or template, creating the document from a template when needed.
create_embedded_editor
Approval: see the ruleCreates a link to an editor where you place or adjust fields on a document, group or template. Starting from a template, it builds the document first.
create_from_template
Approval: see the ruleMakes a new document, or a group, out of one of your templates. The template supplies the layout;
update_document_fields
Approval: see the ruleWrites values into the text fields of a single document, such as a name or a date, before it is sent.
Not documented (4)
4 toolsThe directory publishes these four names and nothing more. SignNow's tool page does not describe them, and this page will not guess from a name.
send_invite_from_template
Listed in the directory, absent from SignNow's tool page, and described by no Claude page either. That is all anyone can say about it for now.
create_embedded_sending_from_template
Another name the directory shows without a word of explanation. SignNow's documentation skips it, so this page does not fill the gap with a guess.
create_embedded_editor_from_template
Nothing official documents this one: no description on the directory sheet, none in SignNow's tool reference, none at Anthropic. The gap is real, not an oversight on this page.
create_embedded_invite_from_template
The fourth name that appears only as a label on the directory sheet. No source, from SignNow or Anthropic, says anything about it, so neither does this page, even briefly.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it carries out on an account for you. The request shows up in the conversation, at the moment it matters.
On Team and 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 organisation, keeping reading open and closing writing, for example. That setting applies to everyone and nobody gets around it from their own account. And Claude works with your rights, nothing more: what you cannot reach in SignNow stays out of its reach too.
Which plans it works on
None of the 819 sheets in the official directory shows availability by plan. The answer, connector by connector, is not published anywhere: it is a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organisation before members can connect. For the current state, check the connector'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 starts when a signer finishes, a document expires or a new template appears.
The tool list is an observed floor, not a promise: an administrator can open actions that no public sheet shows. The partner badge in the directory is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as described. Everything below comes from SignNow's documentation, since neither Claude's help centre nor Anthropic's docs have a page on this connector. For another connector where writing needs care, see the Claude bamboohr connector.
Need help connecting SignNow to Claude?
A person reads every message.
