Claude Send connectorWhat Claude can do in your Send account.
The Claude Send connector exposes 2 tools. 0 only read, 2 change something in your Send account, 0 are undocumented. Below: what Claude publishes for you, what it edits, what it asks first, and where Send's own app takes over.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can publish to Send
You describe a proposal, a one-pager or a report in the chat, and Claude writes it as a self-contained HTML page that Send stores and returns as a shareable link. No hosting to set up, no file to export: the result of the conversation already has an address you can paste into an email.
A client proposal with its own URL. With CreateDocument, Claude hands Send a complete HTML page and gets back the link plus an identifier it keeps for later changes. Send can also start from a copy of a document that already exists, when you pass its link.
Fixing a page after it went out. A mistake spotted after the link went out: EditDocument applies a small targeted change to a document you own, and the same link now shows the new version. No second URL to circulate.
Knowing who opened it. Send records each view of the link (who, when, how long) and notifies the owner. That tracking lives in the Send app, not in the conversation.
What Claude does not do here: the directory sheet lists no tool that reads your view statistics, sets up the lead-capture form or lists your existing documents, so those stay in Send itself. Nothing runs in the background either: Claude acts only while it answers you. For a job that should fire on its own when something happens, an automation tool is the right fit, a different trade; the Integrations hub gathers that side.
Five terms before you start
The words you will meet while plugging Send 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 a connector opens to Claude. Claude picks the ones it needs by itself; the directory sheet lists them by name.
- Authorization
- Send's own sign-in screen, where you hand Claude the access it will use. Given once per person, and it can be taken back.
- Approval
- The confirmation Claude waits for before going through with something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like Send.
Plug Send into Claude in three steps
- 01
Find Send among your connectors
In Claude's settings, open Customize, then Connectors, and look for Send. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first before each member can sign in.
- 02
Start the connection
Click Connect on Send's row and sign in through the window Send opens itself. If the link ever breaks, the fix is to use Disconnect, then plug Send back in from that same row.
- 03
Read the authorization screen
Check Send's authorization screen before you accept. It belongs to Send, not to Claude, and it sets what the access covers. You can also withdraw that access later from your Send account.
The 2 Send tools, sorted by what they do
Send gives Claude 2 tools: 0 that read your account, 2 that change something in it.
Both tools change something in your Send account. Their names stay in English, exactly as Claude shows them.
- 2 write
What Claude changes (2)
2 toolsTwo tools that publish or modify a document. No source describes a confirmation specific to either one: the general rule below applies.
CreateDocument
Approval: see the rulePublishes a new Send document from a complete HTML page written in the chat, or duplicates an existing document from its link. Claude gets back the shareable URL and an identifier for later edits.
EditDocument
Approval: see the ruleChanges a document you own with a small, targeted edit rather than a full rewrite. The link you already shared is updated where it stands, so readers see the new version at the same address.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before each action it takes on an account on your behalf. The request shows up in the conversation, at the moment it counts.
On Team and Enterprise workspaces, owners decide whether members may let some actions through without being asked every time. They can also restrict what a connector may do for the whole organization, for example keeping reads and closing writes; nobody overrides that from their own account. Claude works with your Send rights and nothing more: a document you could not edit yourself stays out of its reach.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. That answer is published nowhere, connector by connector: a real gap in the catalogue, not in our research.
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 enables the connector for the organization before members can connect one by one. For Send's current status on your account, check its 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 on its own when a reader opens your link.
The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The directory's verification badge is not a security audit either; Anthropic states on every sheet that it does not choose the tools a publisher exposes or guarantee how they behave. This connector is documented only by Send, on its own MCP page: no Claude help article covers it, so what Send writes there is all we can rely on.
Need help connecting Send to Claude?
A person reads every message.
