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
Account Custom Field → Update
AI-generatedSummary
Updates an existing account-level custom field definition in DocuSign by its field ID, changing its name, required flag, UI visibility, or list values.
Inputs
- authentication — Authentication method: JWT (Service Integration, default) or OAuth2 (User Authorization).
- fieldId (required) — ID of the account custom field to update.
- updateFields — Collection of optional changes: Field Name (new name), Required (boolean), Show in UI (boolean, default true), and List Items (comma-separated values for list-type fields).
Output shape
The DocuSign API response for the updated account custom field, returned as the node's output item.
The per-operation handler body (handleAccountCustomFieldUpdate) is not visible in the provided source, so the exact request mapping and response fields are not confirmed. Errors are raised with added context unless continue-on-fail is enabled.
Examples
Example 1: Rename an account custom field and make it required.
Field ID = the custom field's ID; Update Fields: Field Name = 'Department', Required = true.
Example 2: Replace the dropdown values of a list-type custom field.
Field ID = the field's ID; Update Fields: List Items = 'Sales,Legal,Finance'.