Actions198
- Account Custom Field Actions
- Account Group Actions
- Account Settings Actions
- Account Signature Actions
- Account User Actions
- Account Watermark Actions
- Billing Actions
- Brand Actions
- Bulk Send Actions
- Captive Recipient Actions
- Chunked Upload Actions
- Cloud Storage Actions
- Comments Actions
- Composite Template Actions
- Connect Configuration Actions
- Connect Event Actions
- Consumer Disclosure Actions
- Contact Actions
- Custom Tab Actions
- Diagnostics Actions
- Document Generation Actions
- Email Archive Actions
- Envelope Actions
- Envelope Purge Actions
- Envelope Attachment Actions
- Envelope Custom Field Actions
- Envelope Document Field Actions
- Envelope Email Setting Actions
- Envelope Lock Actions
- Envelope Notification Actions
- Envelope Transfer Actions
- Folder Actions
- ID Verification Actions
- Notary Actions
- Notary Journal Actions
- Payment Tab Actions
- Permission Profile Actions
- PowerForm Actions
- Recipient Tabs Actions
- Reporting Actions
- Scheduled Routing Actions
- Signing Group Actions
- Supplemental Document Actions
- Template Actions
- Template Bulk Recipient Actions
- Template Custom Field Actions
- Template Document Actions
- Template Lock Actions
- Template Notification Actions
- Template Recipients Actions
- Template View Actions
- Trust Service Provider Actions
- Workspace Actions
- Organization Actions
Envelope → Get
AI-generatedSummary
Retrieves a single DocuSign envelope by its ID via the DocuSign eSignature API, returning the envelope's details.
Inputs
- Envelope ID (required) — The ID of the envelope to retrieve. It is validated before the request, since DocuSign envelope IDs are UUIDs.
- Authentication — Credential type used for the API call: JWT (Service Integration, the default) or OAuth2 (User Authorization).
Output shape
A single record: the envelope object as returned by DocuSign's envelope GET endpoint (for example status, subject and timestamps).
The source pack shows only the handler name (handleEnvelopeGet), not its body. The exact fields and any extra query parameters, such as included recipients or documents, are therefore not confirmed here. Requests go through the shared helper, which retries on rate limits (429) and 5xx errors. A non-existent or unauthorized envelope raises an error.
Examples
Example 1: Check whether an envelope has been completed after a webhook trigger.
Resource: Envelope, Operation: Get, Envelope ID set to an expression such as {{$json.envelopeId}}, Authentication: JWT.
Example 2: Look up the status of an envelope created earlier in the workflow.
Envelope ID mapped from the output of the Envelope Create node.