ElevenLabs icon

ElevenLabs

WIP

Actions16

Overview

The "Get Voice Details" operation in the ElevenLabs node retrieves detailed information about a specific generated voice by its unique identifier. This is useful for users who want to inspect or manage voices they have created or have access to within the ElevenLabs platform. For example, you might use this node to fetch metadata or settings of a voice before using it in text-to-speech synthesis or to audit voice configurations.

Properties

Name Meaning
This node is currently in BETA and under active development.
Visit this page for more information or contact the n8Ninja on X.

To support my work, please share this youtube video 🥷🙏		 Informational notice about the node's development status and support links.
With Settings Boolean option to specify whether to include voice settings in the returned details.
Generation Voice ID The unique identifier (generated_voice_id) of the generated voice whose details are requested. This is a required string input.

Output

The output JSON contains detailed information about the specified generated voice. If the "With Settings" property is enabled, the output will also include the voice's configuration settings. The exact structure depends on the API response but typically includes fields such as voice name, language, gender, and any custom settings associated with the voice.

If the node supports binary data output (not indicated here), it would represent audio or related media, but this operation primarily returns JSON metadata.

Dependencies

  • Requires an API key credential for ElevenLabs API authentication.
  • The node makes HTTP POST requests to the ElevenLabs API endpoint at https://api.elevenlabs.io/v1.
  • No additional external dependencies are indicated.

Troubleshooting

  • Missing or invalid generated_voice_id: The node requires a valid voice ID; ensure this is correctly provided to avoid errors.
  • API authentication errors: Verify that the API key credential is correctly configured and has necessary permissions.
  • Network or API downtime: Temporary connectivity issues or API service interruptions may cause failures; retry after some time.
  • Unexpected response format: Since the node is marked as BETA and under active development, API changes might affect output; check for updates or node version upgrades.

Links and References

Discussion