Short answer: Drop the "DocuSign → Void DocuSign Envelope" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Account ID account_id | string | Required | Your DocuSign account ID (GUID) |
Envelope ID envelope_id | string | Required | The ID of the envelope to void |
Void Reason voided_reason | string | Required | Reason for voiding the envelope |
{"account_id": "e.g. ae34abc5-1234-5678-abcd-1234567890ab","envelope_id": "e.g. a1b2c3d4-5678-90ab-cdef-1234567890ab","voided_reason": "Contract terms changed"}
{"status": "voided","envelopeId": "a1b2c3d4-5678-90ab-cdef-1234567890ab","voidedReason": "Contract terms changed","voidedDateTime": "2026-04-23T12:00:00.0000000Z"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.