ElevenLabs icon

ElevenLabs

Generate natural-sounding speech using ElevenLabs AI
Join our community

Actions13

Overview

The "Get History Audio" operation of the ElevenLabs node allows users to retrieve audio files from their generation history stored on the ElevenLabs platform. This is useful for accessing previously generated speech audio without needing to regenerate it, saving time and API usage. Typical scenarios include replaying or downloading past text-to-speech outputs, archiving generated audio, or integrating historical audio data into workflows.

For example, a user who has generated multiple voice clips can use this operation to fetch a specific clip by its history item ID and then use it in further processing or playback within n8n.

Properties

Name Meaning
History Item ID The unique identifier of the history item (audio) you want to retrieve.
Binary Name (Optional) The name to assign to the binary output data. Defaults to "data".
File Name (Optional) The filename to assign to the downloaded audio file. Defaults to "voice".
API Key Notice Informational notice that an API key from ElevenLabs is required to use this node.

Output

The node outputs the retrieved audio file as binary data. The binary data contains the audio content corresponding to the specified history item ID. The binary property name defaults to "data" but can be customized via the "Binary Name" input property. The filename of the binary data can also be set, defaulting to "voice".

The JSON output field typically includes metadata about the retrieved audio, such as the history item ID or other relevant details, but the main payload is the binary audio data itself.

Dependencies

  • Requires an active ElevenLabs account with a valid API key.
  • The API key must be configured in n8n credentials to authenticate requests.
  • Internet access to call the ElevenLabs API endpoint at https://api.elevenlabs.io/v1.

Troubleshooting

  • Missing or invalid API key: The node will fail if the API key is not provided or invalid. Ensure the API key credential is correctly set up in n8n.
  • Invalid History Item ID: If the provided history item ID does not exist or is malformed, the API will return an error. Verify the ID before using it.
  • Network issues: Connectivity problems may cause request failures. Check network settings and API availability.
  • Binary output naming conflicts: If multiple nodes output binary data with the same name, consider customizing the "Binary Name" property to avoid overwriting.

Links and References

Discussion