Actions16
Overview
The "Create Voice" operation in the ElevenLabs node allows users to create a new voice entry in their voice library by using a previously generated voice ID. This is useful for managing custom voices that have been generated and want to be saved or reused later. For example, after generating a unique voice with the "Generate Voice" operation, you can create and store it under a specific name and description for future text-to-speech tasks.
Common scenarios include:
- Saving a newly generated custom voice for repeated use.
- Organizing multiple custom voices with descriptive labels.
- Cloning or creating voices programmatically within an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Generation Voice ID | The unique identifier (generated_voice_id) of the voice generated earlier to be created. |
| Name | The display name for the new voice (default: "n8n voice"). |
| Description | Optional description of the voice (default: "Generate with n8n"). |
| Labels (JSON) | JSON object containing up to 5 labels describing the voice, e.g., language, descriptive tags. |
Additionally, there is a notice property informing users that this node is in BETA and under active development, with links for more information and support.
Output
The node outputs JSON data representing the created voice object. This typically includes details such as the voice's ID, name, description, labels, and other metadata returned from the API after successful creation.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for ElevenLabs API authentication.
- The node makes HTTP POST requests to
https://api.elevenlabs.io/v1. - No additional environment variables are explicitly required beyond the API key.
Troubleshooting
- Invalid or missing
generated_voice_id: Ensure the voice ID provided corresponds to a valid generated voice. Errors may occur if the ID is incorrect or expired. - API authentication errors: Verify that the API key credential is correctly configured and has necessary permissions.
- Malformed JSON in Labels: If providing labels, ensure the JSON is well-formed and does not exceed the maximum allowed number of labels (5).
- Beta status warnings: Since the node is in active development, some features might be unstable or change; check the linked resources for updates.