ActionDocuSignUpdated September 2026
How do I send a DocuSign envelope?
Short answer: You can send envelope in DocuSign by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the DocuSign Send Envelope action to a workflow, map its 6 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Account ID account_id | string | Required | Your DocuSign account ID (GUID). Found in DocuSign Admin → API and Keys. |
Email Subject email_subject | string | Required | Subject line for the signature request email |
Signer Email signer_email | string | Required | Email address of the signer |
Signer Name signer_name | string | Required | Full name of the signer |
Document (Base64) document_base64 | string | Required | Base64-encoded content of the document to be signed |
Document Name document_name | string | Required | File name of the document (e.g. Contract.pdf) |
Sample request
{"account_id": "e.g. ae34abc5-1234-5678-abcd-1234567890ab","email_subject": "Please sign this document","signer_email": "signer@example.com","signer_name": "John Doe","document_base64": "{{trigger.document_base64}}"}
Returns
{"uri": "/envelopes/a1b2c3d4-5678-90ab-cdef-1234567890ab","status": "sent","envelopeId": "a1b2c3d4-5678-90ab-cdef-1234567890ab","statusDateTime": "2026-04-23T10:30:00.0000000Z"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Send Envelope.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Send Envelope.
What does the Send Envelope action do in DocuSign?
Creates and sends an envelope from a template or raw document. Optional templateRoles map template roles to actual signer emails. The standard contract-send workflow once you have the template designed in DocuSign admin.
What inputs does Send Envelope require?
Required: Account ID, Email Subject, Signer Email, Signer Name, Document (Base64), Document Name. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if DocuSign returns an error?
The run history shows the failed step with its input and the error message DocuSign returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Send Envelope support batch operations?
Run Send Envelope inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within DocuSign's rate limits.
More actions
Other DocuSign actions.
Action
Get Envelope
Returns the envelope with per-recipient status, audit trail, and documents. The standard lookup for "is the envelope signed yet?" polling workflows or for round-tripping back to fetch the completed PDF.
ActionList Envelopes
Returns paginated envelopes with filters by status, sender, recipient email, time range. Useful for "all outstanding contracts" reporting and for "envelopes idle 7+ days" reminder workflows.
ActionVoid DocuSign Envelope
Voids an in-flight envelope with a required voidedReason string. Recipients who haven't signed receive a void notification. Useful for "wrong recipient, abort" workflows or "terms changed before signing, restart" cases.