Actions13
- Speech Actions
- Voice Actions
- History Actions
- User Actions
User → Get User Info
AI-generatedOverview
The node integrates with the ElevenLabs API, focusing on various resources including Speech, Voice, History, and User. Specifically for the User resource with the Get User Info operation, it retrieves information about the authenticated user from the ElevenLabs service.
This node is useful in scenarios where you need to programmatically access user account details such as subscription status, usage limits, or profile information within an automation workflow. For example, you might use it to verify user account status before performing speech synthesis tasks or to log user metadata for auditing purposes.
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 "Get User Info" are not explicitly listed here but would typically include authentication credentials handled internally.
Output
The node outputs JSON data containing the user's information retrieved from the ElevenLabs API. This typically includes fields such as user ID, email, subscription details, usage statistics, and other profile-related data.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating requests to the ElevenLabs API.
- The node sends HTTP POST requests to
https://api.elevenlabs.io/v1. - Proper configuration of the API key credential in n8n is necessary for successful execution.
Troubleshooting
Common Issues:
- Authentication failures due to missing or invalid API key.
- Network connectivity issues preventing access to the ElevenLabs API endpoint.
- Receiving incomplete or unexpected user data if the API changes or the user account lacks certain information.
Error Messages:
- Unauthorized or 401 errors indicate problems with the API key; ensure the correct key is configured.
- Timeout or network errors suggest connectivity problems; verify internet access and API availability.
- Unexpected response formats may require checking for updates in the node or API version compatibility.