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
Template Recipients → Get Many
AI-generatedSummary
Retrieves all recipients defined on a DocuSign template, given its template ID. The source pack shows only the handler name (handleTemplateRecipientsGetAll), not its body, so exact endpoint and response shape are inferred from the name.
Inputs
- Authentication — Credential method: JWT (Service Integration, default) or OAuth2 (User Authorization).
- Template ID (required) — The ID of the DocuSign template whose recipients should be listed.
Output shape
Recipient data for the specified template, as returned by the DocuSign API (likely grouped by recipient type such as signers and carbon copies).
The handler body isn't included in the source pack, so the exact output structure and any pagination are unconfirmed. Requests go through the node's shared API helper, which retries on rate limits (429) and 5xx errors.
Examples
Example 1: Inspect the roles and recipients on a template before creating an envelope from it.
Resource: Template Recipients; Operation: Get Many; Template ID: the template's ID (e.g. from a Template Get Many step).