DocuSignInstall

Summary

Creates a DocuSign focused (embedded signing) view URL for a specific recipient of an existing envelope, intended for display in an iframe within your own app. The handler body (handleEnvelopeCreateFocusedView) is not included in the source pack, so the details below are based on the declared parameters.

Inputs

• Authentication — JWT (service integration, default) or OAuth2 (user authorization) credential type.
• Envelope ID (required) — ID of the envelope to create the focused view for.
• Signer Email (required) — Email of the signer; must match a recipient in the envelope.
• Signer Name (required) — Name of the signer; must match a recipient in the envelope.
• Return URL (required) — URL the signer is redirected to after signing finishes.
• Client User ID — Unique identifier for the embedded signing session. The recipient must be set up as embedded (with a client user ID) for this flow.
• Frame Ancestors — Comma-separated origins allowed to host the view in an iframe. Defaults to * (all).
• Message Origins — Comma-separated origins allowed to receive postMessage events from the view. Defaults to * (all).

Output shape

A single item containing the DocuSign API response for the focused view request, expected to include the signing URL to embed in an iframe.

Exact response fields are not confirmed from the source shown. Embedded URLs from DocuSign are typically short-lived and single-use, so generate them right before displaying. Restrict Frame Ancestors and Message Origins to your own domains rather than * in production.

Examples

Example 1: Embed signing inside a web portal after creating an envelope

Envelope ID from the Create step, Signer Email/Name matching the recipient, Client User ID 'user-123', Return URL https://yourapp.com/signing-complete, Frame Ancestors https://yourapp.com, Message Origins https://yourapp.com.

Links

• n8n community nodes installation guide