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 → Delete
AI-generatedSummary
Deletes a single custom field from a DocuSign template, identified by template ID and field ID. The handler body (handleTemplateCustomFieldDelete) isn't shown in the source pack, so the exact API call is inferred from the declared parameters.
Inputs
- authentication — Auth method: JWT (Service Integration, default) or OAuth2 (User Authorization).
- templateId (required) — ID of the template that owns the custom field.
- fieldId (required) — ID of the custom field to delete.
Output shape
One output item per input item, containing the API response for the delete call (likely empty or a confirmation object).
The handler body isn't visible in the source pack, so the exact return shape is unconfirmed. Failures raise an error unless the node's continue-on-fail setting is enabled. Requests are retried on rate limiting (429) and server errors (5xx).
Examples
Example 1: Remove an obsolete metadata field from a template
Resource: Template Custom Field, Operation: Delete, Template ID: the template's ID, Field ID: the custom field's ID (e.g. from the Get operation).