DocuSealInstall

Summary

Create a DocuSeal signature submission from one or more HTML documents, then configure its signers, notifications, and signing options. The node sends the submission to DocuSeal and returns the API response.

Inputs

• Authentication (required) — Choose Access Token or OAuth2 credentials.
• Documents (required) — Add HTML documents with field tags. HTML Content is required for each document; optionally set its name, header and footer HTML, page size, and position.
• Signers (required) — Add signers with an email and role. Optionally set their name, phone, external ID, metadata, redirect and reply-to addresses, email or phone 2FA, per-signer email/SMS notifications, auto-sign completion, and pre-filled field values.
• Submission Name — Name for the submission.
• Send Email — Send notification emails to signers; defaults to true.
• Send SMS — Send signature requests by SMS; defaults to false.
• Email Subject and Email Body — Set both to include a custom notification message; the source only sends the message when both are non-empty.
• Template IDs — Comma-separated template IDs to merge with the HTML documents.
• Signers Order — Choose Preserved for sequential signer notifications or Random for notifying all parties right away; defaults to Preserved.
• BCC Email Address — Address to BCC with signed documents after completion.
• Reply-To Email Address — Reply-to address for notification emails.
• Redirect URL — URL to redirect signers to after signing.
• Expire At — ISO 8601 expiration datetime after which the submission is unavailable for signing.
• Merge Documents — Merge the documents into one PDF; defaults to false.

Output shape

A single item containing the DocuSeal API response as JSON for each input item.

The operation posts to DocuSeal's /submissions/html endpoint. Empty optional values are omitted; the response fields depend on the API.

Links

• n8n community nodes installation guide