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
Bulk Send → Create List
AI-generatedSummary
Creates a DocuSign bulk send list with a name and a set of recipients (email, name, template role), for later use with the Bulk Send "Send" operation.
Inputs
- authentication — Auth method: JWT (service integration, default) or OAuth2 (user authorization).
- listName (required) — Name of the bulk send list.
- recipients (required) — One or more recipients to include. Each has a required Email, a required Name, and an optional Role Name (defaults to "Signer") that should match a role in the template you plan to send.
Output shape
Presumably the DocuSign API response for the newly created bulk send list, including the list ID needed for later operations.
The handler body is not visible in the provided source pack, so the exact response fields and request mapping are not confirmed. Errors from the DocuSign API are surfaced as node errors.
Examples
Example 1: Build a distribution list of employees to receive a policy acknowledgment form.
List Name: "Policy Acknowledgment Q4"; Recipients: add one entry per employee with Email and Name, Role Name "Signer".