ElevenLabs icon

ElevenLabs

WIP

Actions13

Overview

The Clone Voice operation in the "Voice" resource of this custom n8n node allows users to create a new voice by cloning an existing one using the ElevenLabs API. This is particularly useful for scenarios where you want to duplicate a voice profile, perhaps to experiment with different settings or to use as a template for further customization.

Practical examples:

  • Duplicating a voice for A/B testing different speech synthesis parameters.
  • Creating backup versions of a voice before making significant changes.
  • Generating multiple similar voices for different projects or clients.

Properties

Display Name Type Meaning
Notice notice Informational message about the node's beta status, support links, and latest updates.
Name string The name for the cloned voice.
Additional Fields collection Optional extra fields for the voice, such as description and labels.
└─ Description string A description for the cloned voice.
└─ Labels (JSON) json JSON object with up to 5 labels describing the voice (e.g., language, style).

Output

The output will be a json object containing details of the newly cloned voice. While the exact structure depends on the ElevenLabs API response, it typically includes:

{
  "voice_id": "string",
  "name": "string",
  "description": "string",
  "labels": {
    "language": "string",
    "descriptive": "string",
    "generated": "string"
  },
  // ...other metadata fields returned by the API
}
  • If the node supports binary data output, it would likely relate to audio files generated from the voice, but for the Clone Voice operation, the main output is JSON metadata about the new voice.

Dependencies

  • External Service: Requires access to the ElevenLabs API.
  • API Key: You must configure valid ElevenLabs API credentials in n8n (elevenLabsApi).
  • n8n Configuration: No special environment variables are required beyond standard credential setup.

Troubleshooting

Common issues:

  • Invalid API Key: If your API key is missing or incorrect, the node will fail to authenticate. Ensure your credentials are set up correctly in n8n.
  • Missing Required Fields: If the "Name" property is not provided, the API may reject the request.
  • Malformed Labels JSON: If the "Labels (JSON)" field contains invalid JSON, the node will throw a parsing error. Always ensure your JSON is properly formatted.

Error messages you might encounter:

  • "401 Unauthorized": Check your API credentials.
  • "400 Bad Request": Review required fields and JSON formatting.
  • "429 Too Many Requests": You have hit the API rate limit; try again later.

Links and References

Discussion