Docusign
Integrates with the Docusign eSignature API to manage the full document signing lifecycle. Create envelopes with local documents (PDF, DOCX, etc.) or from pre-built templates, send them for signature, track envelope status, download signed documents, and void in-progress envelopes. Supports template management with role-based recipient assignment and CC recipients. Authenticates via OAuth2 with PKCE, supporting both demo/sandbox and production environments. Connect node is optional — credentials can be provided directly on each node.
| Namespace | Robomotion.Docusign |
| Version | 1.1.0 |
| Category | eSignature, Business Software |
| Nodes | 12 |
Nodes
| Node | Description |
|---|---|
| Connect | Opens a connection to Docusign and returns a Client ID. |
| Disconnect | Closes a Docusign connection. |
| Create Envelope | Creates an envelope in Docusign. |
| Create Envelope from Template | Creates an envelope from template in Docusign. |
| Send Envelope | Sends an envelope in Docusign. |
| Get Envelope | Gets an envelope in Docusign. |
| List Envelopes | Lists envelopes in Docusign. |
| Download Document | Downloads a document in Docusign. |
| Void Envelope | Void Envelope — see the properties below. |
| List Templates | Lists templates in Docusign. |
| Get Template | Gets a template in Docusign. |
| Toolkit | Exposes this package's operations to an AI Agent as a single tool. |
Connecting
This package has a Connect node. Run it once at the start of your flow; it returns a Client ID that the other nodes take as input. Pair it with Disconnect so the connection is released when the flow ends.
Credentials belong in a Vault rather than typed into the node.
AI Agent tools
11 of these nodes are exposed as tools an AI Agent can call directly:
Connect, Disconnect, Create Envelope, Create Envelope from Template, Send Envelope, Get Envelope, List Envelopes, Download Document, Void Envelope, List Templates, Get Template.
Generated from the package spec that the Flow Designer itself loads, so the node list and every property below match the version above exactly.
It does not yet include worked examples or service-specific guidance — those are written by hand, and a plausible-sounding guess in a reference page is worse than an honest gap. If you build something useful with this package, the community is the place to share it.