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 Settings → Update
AI-generatedSummary
Updates account-level settings in the connected DocuSign account by sending a user-supplied JSON object of setting names and values.
Inputs
- Authentication — Credential type used for the request: JWT (Service Integration, the default) or OAuth2 (User Authorization).
- Settings JSON (required) — JSON object of account settings to update, e.g. {"enableSequentialSigningAPI": "true"}. Keys must be valid DocuSign account setting names.
Output shape
The DocuSign API response for the account settings update, returned as an n8n item.
The source pack shows only the handler name (handleAccountSettingsUpdate), not its body. The exact endpoint, how the JSON is parsed and the response fields are not visible. Invalid JSON or rejected setting names will probably cause an error. Requests go through the node's shared API helper, which retries on rate limits and 5xx errors.
Examples
Example 1: Enable the sequential signing API for the account.
Resource: Account Settings; Operation: Update; Settings JSON: {"enableSequentialSigningAPI": "true"}