We need a Docusign integration, I don’t understand how this massive opportunity is not here, Love N8N - Hate we don’t have it already…
We need to create a contract to send out on new customer signup, we don’t have that yet and it’s bananas.
Everyone must have a document signing need and DocuSign is the industry leader.
Oh if I could…
I’ve never heard of Docusign, but i know that people use notion and or google docs templates to fill out the new customers infos and send them documents. This eSignature workflow would be good idea too, I have a background in coding so I will give it a try and share with you how the workflow will be.
It seems that DocuSign now put all of their API access behind an incredibly expensive paywall. We will also review how to do this via e-signature workflow in Google and let you know how we get on.
I have used docuseal in the past, seems to work great.
I build TurboDocx, so we compete in this space. Flagging that up front.
Out of the box, open source signing isn’t tamper-evident, which is the thing that courts, compliance, and disputes actually focus on. With no certificate wired in, a contract signed at $10 can later read $100 and you have no straightforward way to prove which version was signed. That’s the part that doesn’t come up when people recommend self hosting.
@BramKn is right that DocuSeal is worth a look, and it does answer the problem @James_Adams1 hit two posts up. DocuSeal and Documenso are both open source, both have community nodes, and both self host. I’m not against open source here either, we build and maintain a fairly widely used library ourselves.
The catch is that you have to procure a signing certificate and wire it in yourself. Self-signed works technically, but Adobe Reader can’t verify it, so your recipient sees a warning instead of the green tick. What you actually want is a certificate on the Adobe Approved Trust List, plus Long Term Validation so the signature still verifies years later once the certificate has expired. Getting an AATL certificate and keeping the key in a FIPS 140 validated HSM is where the cost really sits. We offer self hosting to paying customers, and once I walk someone through that list, most of them decide the subscription is cheaper than dealing with all of it.
On the signing half generally, as of 2026 there’s still no first party DocuSign node, but there is a community one. If you do end up going straight at DocuSign’s REST API through an HTTP Request node, the only fiddly part is the JWT grant, which is a Code node and about twenty lines. But then you get whacked with enterprise pricing.
The other thing worth separating out, because the thread title buries it: “create a contract to send out on new customer signup” is two problems, and DocuSign only solves one. Sending for signature is the easy half. Producing the contract, merging the signup record into a template so counterparty name, term, pricing and dates come out right, is the half that takes the time. DocuSign will send a document. It will not build one from a CRM row. Whichever signing provider you land on, budget for the generation step separately.
TurboDocx does both halves in one node with a webhook back on completion: TurboDocx integrations | Workflow automation with n8n. The free tier includes 5 signatures a month, which covers a lot of small business volume.