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 → Delete
AI-generatedSummary
Deletes a captive (embedded) recipient in DocuSign, identified by the signer's email address. The handler body is not shown in the source pack, so the exact API call is not visible.
Inputs
- Authentication — Authentication method: JWT (Service Integration, the default) or OAuth2 (User Authorization).
- Signer Email (required) — Email address of the captive recipient to delete. Shared with the Create operation.
Output shape
The DocuSign API response for the delete request, returned as the node's output item. Its exact fields are not visible in the provided source.
The handler (handleCaptiveRecipientDelete) body is not included in the pack, so the endpoint and response fields are unconfirmed. API errors are wrapped with context, and the request helper retries rate-limit (429) and 5xx errors.
Examples
Example 1: Remove a captive recipient after an embedded signing flow is finished or abandoned.
Resource: Captive Recipient, Operation: Delete, Signer Email: {{ $json.email }}