Short answer: Drop the "DocuSign → List Envelopes" 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) |
From Date from_date | string | Required | Start date for the envelope search (ISO 8601 format) |
{"account_id": "e.g. ae34abc5-1234-5678-abcd-1234567890ab","from_date": "2026-01-01T00:00:00Z"}
{"envelopes": [{"status": "completed","envelopeId": "a1b2c3d4-5678-90ab-cdef-1234567890ab","emailSubject": "Please sign this document","sentDateTime": "2026-04-23T10:30:00.0000000Z","completedDateTime": "2026-04-23T11:15:00.0000000Z"},{"status": "sent","envelopeId": "b2c3d4e5-6789-01ab-cdef-2345678901ab","emailSubject": "NDA for review","sentDateTime": "2026-04-22T09:00:00.0000000Z"}],"totalSetSize": "2","resultSetSize": "2"}
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.