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
Billing → Get Plan
AI-generatedSummary
Retrieves the billing plan for the connected DocuSign account. The node dispatches to a dedicated handler, handleBillingGetPlan, which takes no parameters beyond the authentication method.
Inputs
- authentication — Authentication method for the request: JWT (Service Integration, the default) or OAuth2 (User Authorization). Credentials are resolved through the node's shared API helper.
Output shape
The billing plan details returned by the DocuSign API for the account, emitted as a single output item.
The source pack only shows signatures for the handler, not its body, so the exact endpoint and response fields are not visible here. The shared request helper retries on rate limits (429) and 5xx errors, and errors are reported with sanitized messages. The account ID comes from the credentials, so no account parameter is needed.
Examples
Example 1: Check the account's current plan before running a bulk send.
Resource: Billing, Operation: Get Plan, Authentication: JWT (Service Integration).
Example 2: Audit the plan on an account authorized by a user.
Resource: Billing, Operation: Get Plan, Authentication: OAuth2 (User Authorization).