[Community Node] n8n-nodes-docusign-connect — DocuSign eSignature, with JWT auth done properly
Hey all — I built a community node for DocuSign’s eSignature API and just published it: n8n-nodes-docusign-connect.
A few of you have asked for DocuSign support over time, and there are already a couple of early community nodes covering it. This one isn’t trying to be the broadest — it’s deliberately narrow, and focused on the part that actually trips people up: JWT Grant authentication done correctly, including the one-time consent step that’s easy to get wrong on a first setup, plus documentation that walks through DocuSign’s dashboard step by step instead of assuming you already know it.
What it does (one resource, three operations):
| Operation | What it does |
|---|---|
| Create From Template | Fills an existing DocuSign template’s roles and sends it for signature (or saves as a draft) |
| Get Status | Checks whether an envelope is sent, delivered, completed, declined, or voided |
| Download Document | Pulls a signed document back as a binary file — single doc, combined PDF, or certificate of completion |
It also works as a tool for AI Agent nodes out of the box, so an agent can send a contract or check its status directly.
Not in v1, on purpose: raw document upload with anchor tabs, template management, bulk send, embedded signing, and Connect webhooks. If any of those matter to you, say so below — that’s real input for what comes next.
Install: Settings → Community Nodes → n8n-nodes-docusign-connect, or npm install n8n-nodes-docusign-connect for a self-hosted setup.
Full credential setup (Integration Key, RSA key generation, the consent URL) is in the README — it’s about 10 minutes end to end, with one step (the consent click) that has to happen in a real browser and can’t be automated away.
Feedback, bug reports, and “I need X operation” requests are all welcome on the GitHub repo.