Short answer: Drop the "DocuSign → Get 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 retrieve |
{"account_id": "e.g. ae34abc5-1234-5678-abcd-1234567890ab","envelope_id": "e.g. a1b2c3d4-5678-90ab-cdef-1234567890ab"}
{"sender": {"email": "jane@example.com","userName": "Jane Smith"},"status": "completed","envelopeId": "a1b2c3d4-5678-90ab-cdef-1234567890ab","recipients": {"signers": [{"name": "John Doe","email": "signer@example.com","status": "completed","signedDateTime": "2026-04-23T11:15:00.0000000Z"}]},"emailSubject": "Please sign this document","sentDateTime": "2026-04-23T10:30:00.0000000Z","completedDateTime": "2026-04-23T11:15: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.