DocuSignInstall

Summary

Uploads one base64-encoded chunk to an existing DocuSign chunked upload session, identified by the session ID and a zero-based part index. Use it after Initiate and before Commit to send large documents in pieces.

Inputs

• Authentication — Credential type: JWT (Service Integration, the default) or OAuth2 (User Authorization).
• Chunked Upload ID (required) — The session ID returned by the Initiate operation.
• Chunk Part (required) — Zero-based index of the chunk being uploaded (minimum 0, default 0).
• Chunk Data (Base64) (required) — The base64-encoded bytes of this chunk.

Output shape

The DocuSign API response for the chunk upload, returned as the item's JSON. It is most likely chunked upload session details, but the source pack doesn't show the handler body.

The handler (handleChunkedUploadChunk) is not visible in the provided source, so the exact response fields and endpoint are not confirmed. The call goes through the shared DocuSign request helper, which retries on rate limits and 5xx errors. API errors are raised as node errors.

Examples

Example 1: Upload the first chunk of a large PDF after initiating a session.

Chunked Upload ID = {{$json.chunkedUploadId}}, Chunk Part = 0, Chunk Data (Base64) = base64 string of the first slice of the file.

Example 2: Loop over several chunks, then commit.

Run this node once per item, setting Chunk Part to {{$itemIndex}} and Chunk Data to each item's base64 slice. Follow it with the Commit operation.

Links

• n8n community nodes installation guide