DocuSign icon

DocuSign

Send documents for eSignature and manage envelopes with DocuSign

Actions198

Envelope → Create

AI-generated

Summary

Creates a DocuSign envelope from one or more uploaded documents and sends it to a primary signer (plus optional extra signers and a CC), either sending immediately or saving it as a draft.

Inputs

  • emailSubject (required) — Subject line of the email sent to recipients.
  • signerEmail (required) — Email address of the primary signer.
  • signerName (required) — Full name of the primary signer.
  • document (required) — Name of the binary property on the input item that holds the document, or a base64-encoded string.
  • documentName (required) — File name of the document (default document.pdf). The file extension is derived from this name.
  • sendImmediately — If true (default), the envelope is sent on creation. If false, it is left as a draft.
  • additionalOptions — Collection of optional settings. Message and envelope behavior: email message, allow markup, allow reassign, brand ID, wet sign, signer visibility enforcement. Notifications: reminders (delay and frequency) and expiration (expire after and warning days). Recipients: CC email and name, additional signers (email, name, routing order) and signer authentication (access code, phone or SMS). Signature placement: X, Y, page, or an anchor string. Content: additional documents, custom text fields, merge fields (placeholder to value with font size) and additional tabs (initials, date signed, text, checkbox, radio, list, number, formula and others). Delivery and routing: embedded signing with client user ID, SMS delivery, WhatsApp delivery and conditional routing rules.
  • authentication — Credential type used to call DocuSign: JWT (service integration, default) or OAuth2 (user authorization).

Output shape

One output item per input item, containing the DocuSign API response for the created envelope. This is typically the envelope ID, status and URI. I could not confirm the exact shape because the handler body was not visible in the source.

The source pack shows only handler signatures, not their bodies, so the return shape and the exact request fields are inferred from the parameters. Embedded signing adds a clientUserId to the signer. You then need a separate Create Recipient View operation to get the signing URL. SMS and WhatsApp delivery require those features to be enabled in your DocuSign account.

Examples

Example 1: Send a PDF received from a previous node to a customer for signature.

Set Email Subject, Signer Email and Signer Name. Set Document to the binary property name (e.g. data) and Document Name to contract.pdf. Leave Send Immediately on.

Example 2: Create a draft with personalized text, an anchored signature and a reminder.

Turn Send Immediately off. In Additional Options, add Merge Fields for placeholders such as {{FirstName}}, turn on Use Anchor Tag with /sig/, and turn on Send Reminders.

Example 3: Prepare an envelope for embedded signing in your own app.

In Additional Options, turn on Embedded Signing and set a Client User ID. After creation, use the Create Recipient View operation with the same client user ID.

Links

Discussion