DocuSignInstall

Summary

Creates an embedded signing URL (recipient view) for a signer on an existing DocuSign envelope, so you can redirect the signer or load the URL in an iframe, then send them to a return URL after signing.

Inputs

• Authentication — Credential type used for the API call: JWT (service integration, default) or OAuth2 (user authorization).
• Envelope ID (required) — ID of the envelope the signer belongs to.
• Signer Email (required) — Email of the signer. It must match a recipient already on the envelope.
• Signer Name (required) — Name of the signer. It must match a recipient already on the envelope.
• Return URL (required) — URL the signer is redirected to when signing ends. It is validated as a URL, and the source's URL check blocks localhost and private network addresses.
• Authentication Method — How the signer was authenticated: None (default), Email, Password, Phone, or ID Check.
• Client User ID — Identifier for the embedded signing session. If left empty, the node generates one. It must match the clientUserId set on the recipient when the envelope was created, which is the embedded-signing option in Create.

Output shape

A single item containing the DocuSign recipient view response, which includes the signing url.

The exact output shape comes from the DocuSign API response, because the handler body isn't shown in the source pack. The URL is short-lived and meant for one-time use. The call fails if the signer doesn't match an embedded recipient (one with a clientUserId) on the envelope.

Examples

Example 1: Embed signing in your web app right after creating an envelope.

Envelope ID from the Create step output; Signer Email and Name matching the recipient; Return URL https://yourapp.com/signing-complete; Client User ID the same as used at creation.

Example 2: Send a signer through an ID-verified signing session.

Set Authentication Method to ID Check, and fill in Envelope ID, Signer Email, Signer Name and Return URL.

Links

• n8n community nodes installation guide