DocuSignInstall

Summary

Creates a DocuSign envelope from an existing template for a single signer and attaches a payment request (amount, currency, gateway, item name) to it. The source pack shows only the handler's signature (handlePaymentTabCreateEnvelope), not its body, so exact request payload and return shape are not confirmed.

Inputs

• Authentication — Credential type used to call DocuSign: JWT (service integration, default) or OAuth2 (user authorization).
• Email Subject (required) — Subject line of the envelope email sent to the signer.
• Template ID (required) — ID of the DocuSign template the envelope is created from.
• Signer Email (required) — Email address of the signer.
• Signer Name (required) — Full name of the signer.
• Payment Amount (required) — Amount to collect, entered as a string such as "100.00".
• Currency Code — ISO 4217 currency: USD (default), EUR, GBP, CAD, AUD or JPY.
• Payment Gateway ID (required) — ID of the payment gateway account already configured in DocuSign.
• Item Name (required) — Name or description of the item being paid for.

Output shape

Likely the DocuSign API response for the created envelope (e.g. an envelope ID and status), as one item per input item.

Not confirmed from the source, because the handler body is not included. The template must already contain a role and payment tab setup that works with the gateway. Errors from DocuSign are raised with added context unless the node is set to continue on fail.

Examples

Example 1: Send a deposit invoice for signature and payment after a form submission.

Template ID of the deposit agreement, Signer Email and Name from the trigger data, Payment Amount "250.00", Currency USD, Payment Gateway ID from DocuSign, Item Name "Project deposit".

Example 2: Collect a EUR fee when a customer signs a service agreement.

Currency Code EUR, Payment Amount "99.00", Email Subject "Please sign and pay", plus the template and gateway IDs.

Links

• n8n community nodes installation guide