# Best e-signature for n8n

Any e-signature tool with a REST API works in n8n through the HTTP Request node, so pick on API price, test mode and how retries behave, where DocuSeal is cheapest at list, Docusign is the most familiar, and docuinked adds idempotent sends and server-side approval for n8n AI agents.

## How to connect any e-signature tool to n8n

There are three routes, and they work the same whichever vendor you choose.

| Route | What it needs | Good for |
|---|---|---|
| HTTP Request node | A REST API and a key | Fixed workflows: a row, form or deal becomes a contract |
| MCP Client Tool | An MCP server reached by Bearer, header or OAuth2 | n8n AI Agent nodes that prepare documents |
| Community or verified node | A vendor package | Point-and-click setup. Only verified nodes run on n8n Cloud |

So a missing node is less of a gap than it looks. The questions that matter are cost per document, whether you can test without emailing people, and what happens when n8n retries a step.

## The tools in short

All facts below come from vendor pages read on 2026-11-07.

**DocuSeal.** $0.20 a completed document plus at least one $20 Pro seat, with a free sandbox. The lowest known unit price of the big names, and it can run next to a self-hosted n8n.

**SignWell.** 25 free API documents a month on all plans with a card on file, then from $0.85 a document. A simple entry for low volume.

**BoldSign.** $30 a month for 40 envelopes, then $0.75 each, with a free sandbox that is watermarked and deleted after 14 days.

**Docusign.** API plans from $50 a month on annual billing for 40 envelopes, per a third party. Its MCP server post names n8n as a target platform. Its post also says custom agents and scheduled jobs must build their own approval step, which is the n8n AI Agent case.

**docuinked.** First 5 completed documents free, then Personal at $9 a month, with a 100 live sends a day cap. Works today through the HTTP Request node and the MCP Client Tool. A verified n8n node is coming, so there is no node in the panel yet. Three things are built for n8n's habits:

- **Retries send once.** Set the `Idempotency-Key` header from a stable item value. A retried node returns the first result.
- **Test keys email no one.** Run the whole workflow with magic addresses before you go live.
- **Agents can't send alone.** Over MCP, a live send stops at an `approval_url` for a named person. A scheduled agent with no one watching can't email a contract to the wrong person.

The full recipe is on our [n8n page](/integrations/n8n).

## Where others are better

- **You want a node in the panel today.** Check n8n's nodes panel for your vendor. Ours is coming.
- **You want a known price per document.** DocuSeal, SignWell and BoldSign publish one.
- **You send hundreds a day.** Our beta cap is 100 live sends a day per account. Bulk send is coming.
- **Your whole company already signs in Docusign.** Keep templates and records in one place.

## A sample n8n flow with docuinked

1. Trigger: a deal moves to "won" or a form is submitted.
2. HTTP Request: `POST https://docuinked.com/v1/documents` with the PDF link, the signer and `send: true`, keyed by `contract-{{ $json.id }}`.
3. Webhook node: receives `document.completed`. Check the signature in a Code node. See [webhooks](/docs/webhooks).
4. Next step: file the sealed PDF and update the record.

More flows live on the [workflows](/workflows) page.

## Sources

Checked 2026-11-07.

- [n8n MCP Client Tool docs](https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.toolmcp/)
- [n8n community node install docs](https://docs.n8n.io/integrations/community-nodes/installation)
- [DocuSeal pricing](https://www.docuseal.com/pricing)
- [SignWell API pricing](https://www.signwell.com/api-pricing/)
- [BoldSign pricing](https://boldsign.com/pricing/)
- [Signeasy on Docusign API pricing](https://signeasy.com/blog/business/docusign-api-pricing), a third party
- [Docusign MCP general availability post](https://www.docusign.com/blog/developers/docusign-mcp-server-general-availability)

docuinked is not affiliated with or endorsed by n8n or any company named here. All names belong to their owners.

## Common questions

### Do I need a native node to send documents for signature from n8n?

No. The HTTP Request node calls any REST API, and it works on n8n Cloud and self-hosted. A node mainly saves you typing headers and JSON.

### Can unverified community nodes run on n8n Cloud?

Not per n8n's docs. Unverified community nodes need a self-hosted n8n. Verified nodes install from the nodes panel.

### How does an n8n workflow know a document was signed?

Register a webhook with the e-signature tool and point it at an n8n Webhook node. Check the webhook's signature before you act on it, then branch on the event type.

### Should an n8n AI Agent or a fixed workflow send my contracts?

Use a fixed workflow when the template and recipient are known, because it is predictable. Use an agent when it has to read context and assemble the draft, and keep a person approving each send.