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
Chunked Upload → Commit
AI-generatedSummary
Commits (finalizes) a DocuSign chunked upload session so the uploaded chunks are assembled into a single file. Run it after initiating a session and uploading all chunks.
Inputs
- Authentication — Credential type to use: JWT (Service Integration, default) or OAuth2 (User Authorization).
- Chunked Upload ID (required) — The chunked upload session ID returned by the Initiate operation.
- Action — The action to perform. Only 'Commit' (Finalize the upload) is available, and it is the default.
Output shape
A single JSON item containing DocuSign's response to the commit request, typically the chunked upload's updated state.
The handler body is not shown in the provided source, so the exact response fields are not confirmed. API errors are raised with added context, unless the node is set to continue on fail.
Examples
Example 1: Finish uploading a large PDF that was sent in several chunks, before using it in an envelope.
Resource: Chunked Upload; Operation: Commit; Chunked Upload ID: {{ $('Initiate').item.json.chunkedUploadId }}; Action: Commit