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 Custom Field → Get
AI-generatedSummary
Retrieves the custom fields (text and list metadata fields) attached to a single DocuSign envelope, identified by its envelope ID.
Inputs
- authentication — Credential type used for the request: JWT (Service Integration, default) or OAuth2 (User Authorization).
- envelopeId (required) — The ID of the envelope whose custom fields should be fetched.
Output shape
The DocuSign API response for the envelope's custom fields, returned as a single item. This is typically an object with textCustomFields and listCustomFields arrays.
The source pack shows only the handler name (handleEnvelopeCustomFieldGet), not its body, so the exact endpoint and response shape are inferred from DocuSign's API. An envelope with no custom fields likely returns empty arrays. Invalid or unknown envelope IDs produce an API error.
Examples
Example 1: Read an envelope's custom metadata, such as a CRM record ID, after it completes.
Resource: Envelope Custom Field; Operation: Get; Envelope ID set by expression from a previous DocuSign node, e.g. {{ $json.envelopeId }}.
Example 2: Check existing custom fields before updating or deleting one.
Resource: Envelope Custom Field; Operation: Get; Envelope ID: a fixed envelope ID; Authentication: JWT.