Actions198
- Account Custom Field Actions
- Account Group Actions
- Account Settings Actions
- Account Signature Actions
- Account User Actions
- Account Watermark Actions
- Billing Actions
- Brand Actions
- Bulk Send Actions
- Captive Recipient Actions
- Chunked Upload Actions
- Cloud Storage Actions
- Comments Actions
- Composite Template Actions
- Connect Configuration Actions
- Connect Event Actions
- Consumer Disclosure Actions
- Contact Actions
- Custom Tab Actions
- Diagnostics Actions
- Document Generation Actions
- Email Archive Actions
- Envelope Actions
- Envelope Purge Actions
- Envelope Attachment Actions
- Envelope Custom Field Actions
- Envelope Document Field Actions
- Envelope Email Setting Actions
- Envelope Lock Actions
- Envelope Notification Actions
- Envelope Transfer Actions
- Folder Actions
- ID Verification Actions
- Notary Actions
- Notary Journal Actions
- Payment Tab Actions
- Permission Profile Actions
- PowerForm Actions
- Recipient Tabs Actions
- Reporting Actions
- Scheduled Routing Actions
- Signing Group Actions
- Supplemental Document Actions
- Template Actions
- Template Bulk Recipient Actions
- Template Custom Field Actions
- Template Document Actions
- Template Lock Actions
- Template Notification Actions
- Template Recipients Actions
- Template View Actions
- Trust Service Provider Actions
- Workspace Actions
- Organization Actions
Captive Recipient → Create
AI-generatedSummary
Creates a captive (embedded) recipient in DocuSign for a signer, identified by email, name and a client user ID, so that signer can sign via embedded signing. The source pack shows only the handler name (handleCaptiveRecipientCreate), not its body, so the exact API call is not visible.
Inputs
- Authentication — Auth method: JWT (Service Integration, default) or OAuth2 (User Authorization).
- Signer Email (required) — Email address of the signer.
- Signer Name (required) — Full name of the signer.
- Client User ID (required) — Unique ID for the embedded signer. Use the same value when creating an envelope or recipient view for embedded signing.
Output shape
One output item per input item, containing the DocuSign API response for the created captive recipient.
The handler body is not included in the source pack, so the exact response fields are not confirmed. Errors from the DocuSign API are raised as node errors unless Continue On Fail is enabled.
Examples
Example 1: Register a signer for embedded signing inside your own app before sending envelopes.
Signer Email: jane@example.com; Signer Name: Jane Doe; Client User ID: user-1001