Actions16
Overview
The node integrates with the ElevenLabs API, focusing on various resources including speech, voice, history, and user data. Specifically, for the User resource and the Get User Subscription operation, it retrieves subscription details of a user from the ElevenLabs service. This can be useful in scenarios where you want to programmatically check a user's subscription status or plan details within an automation workflow.
Practical examples include:
- Automatically verifying if a user has an active subscription before proceeding with further actions.
- Fetching subscription information to customize content or service access based on the user's plan.
- Monitoring subscription changes as part of a user management system.
Properties
| Name | Meaning |
|---|---|
| notice | A notice indicating that this node is currently in BETA and under active development. It includes links for more information and support. |
Note: The provided properties JSON only contains a notice property. The actual input properties for the "Get User Subscription" operation are defined internally in the bundled code but not explicitly listed here. Typically, such operations require minimal or no additional input beyond authentication.
Output
The node outputs JSON data representing the user's subscription details retrieved from the ElevenLabs API. This typically includes fields such as subscription type, status, expiration date, and any relevant usage limits or features associated with the subscription.
If the node supports binary data output (not indicated in the provided code), it would relate to media or audio files, but for the User Subscription operation, the output is purely JSON-based subscription information.
Dependencies
- Requires an API key credential for ElevenLabs API authentication.
- The node makes HTTP POST requests to
https://api.elevenlabs.io/v1. - No other external dependencies are indicated.
Troubleshooting
Common Issues:
- Invalid or missing API key: Ensure the API key credential is correctly configured in n8n.
- Network connectivity problems: Verify internet access and API endpoint availability.
- API changes during beta: Since the node is in active development, some API endpoints or responses might change.
Error Messages:
- Authentication errors: Check the API key validity and permissions.
- Rate limiting or quota exceeded: Review subscription limits and usage.
- Unexpected response format: May occur if the API changes; verify the node version and update if necessary.