Short answer: Drop the "DocuSign → Send Envelope" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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) |
{"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}}"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.