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
Template Custom Field → Get
AI-generatedSummary
Retrieves the custom fields (custom metadata) defined on a DocuSign template, identified by its template ID. The source shows only a handler stub (handleTemplateCustomFieldGet), so the exact endpoint is inferred.
Inputs
- Template ID (required) — ID of the DocuSign template whose custom fields should be retrieved.
- Authentication — Credential type used for the request: JWT (Service Integration, default) or OAuth2 (User Authorization).
Output shape
The custom field data for the template as returned by the DocuSign API, typically text and list custom field entries. Returned as the node's output item(s).
The handler body is not included in the source pack, so the exact response shape is not confirmed. Requests go through the shared DocuSign API helper, which retries on rate limits (429) and 5xx errors. Failures such as an invalid template ID surface as node errors.
Examples
Example 1: Read the custom metadata on a template before creating an envelope from it.
Resource: Template Custom Field; Operation: Get; Template ID set to the template's GUID (for example via an expression from a prior Template Get Many node).