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 User → Create
AI-generatedSummary
Creates a new user in the connected DocuSign account from an email address and full name, with optional company, job title and activation access code. The source pack shows only the handler's signature (handleAccountUserCreate), not its body, so the exact API call and return shape are not visible.
Inputs
- Authentication — Credential mode: JWT (Service Integration, the default) or OAuth2 (User Authorization).
- Email (required) — Email address of the new user.
- User Name (required) — Full name of the new user.
- Additional Options — Optional collection with Activation Access Code (code used to activate the account), Company, and Job Title.
Output shape
Presumably the DocuSign API response for the newly created user, returned as n8n item JSON. This is not confirmed by the source pack.
The handler body is not included in the source pack, so the exact fields returned (for example user ID, status) are unverified. Errors from the DocuSign API, such as an invalid email or insufficient admin rights, surface as node errors. The API call goes to the account context of the configured credentials.
Examples
Example 1: Provision a DocuSign user when a new employee is added to an HR system.
Email and User Name mapped from the trigger data; Additional Options: Company and Job Title set.
Example 2: Create a user who must enter a code to activate their account.
Set Email and User Name, then add Activation Access Code under Additional Options.