DocuSealInstall

Summary

Create a DocuSeal signature submission from a selected template, configure its signers and pre-filled values, and send signing notifications according to the chosen settings.

Inputs

• Authentication — Choose Access Token (default) or OAuth2 credentials.
• Template Name or ID (required) — Select a DocuSeal template or provide its ID.
• Signers (required) — Add signers with required email and role. Optionally set their name, phone, external ID, metadata, field values to pre-fill, auto-sign status, notification preferences, redirect and reply-to addresses, and email or phone two-factor authentication.
• Email Subject and Email Body — Set both to include a custom notification message; the operation sends the message only when both are provided.
• Send Email — Whether to email each signer; defaults to true.
• Send SMS — Whether to send signature requests by SMS; defaults to false.
• Signers Order — Preserved (default) notifies signers in the configured order, one after the previous signer completes. Random notifies all parties right away.
• Variables — Set key/value variables for dynamic content in the template.
• 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.

Output shape

A single JSON item per input item, containing the DocuSeal API response for the created submission.

The node sends a POST request to DocuSeal's /submissions/init endpoint. Empty optional values are omitted from the request.

Links

• n8n community nodes installation guide