DocuSignInstall

Summary

Adds a new document to an existing DocuSign template, using base64-encoded content supplied in the node parameters. The source pack only shows handler signatures, so the exact API call isn't visible.

Inputs

• Authentication — Credential mode: JWT (service integration, default) or OAuth2 (user authorization).
• Template ID (required) — ID of the template to add the document to.
• Document Name (required) — Name of the document as it will appear in the template.
• Document Content (Base64) (required) — Base64-encoded file content. Pass it as a string, for example from an expression that converts a prior node's binary data.
• File Extension — File type of the document, such as pdf or docx. Defaults to pdf.
• Document Order — Position of the document within the template. Minimum 1, default 1.

Output shape

The DocuSign API response for the add-document call, returned as the node's output item. It is likely to describe the template's documents, but the exact fields aren't visible in the provided source.

The handler body (handleTemplateDocumentAdd) is not included in the pack, so the exact endpoint and response fields are unconfirmed. Errors from DocuSign (invalid template ID, bad base64, and so on) are raised as node errors, and the shared request helper retries on rate limits and 5xx responses.

Examples

Example 1: Attach a generated PDF contract to an existing template

Template ID = existing template ID; Document Name = 'Service Agreement'; Document Content (Base64) = base64 string from a previous node; File Extension = pdf; Document Order = 1.

Example 2: Add a Word document as the second document in a template

Template ID set; Document Name = 'Appendix A'; Document Content (Base64) = base64 of the .docx; File Extension = docx; Document Order = 2.

Links

• n8n community nodes installation guide