Actions13
- Speech Actions
- Voice Actions
- History Actions
- User Actions
Overview
The "Get History Audio" operation of the ElevenLabs node allows users to retrieve audio data associated with a specific history item from their ElevenLabs account. This is useful for accessing previously generated or processed audio clips stored in the user's history, enabling workflows that require reusing or analyzing past audio outputs without regenerating them.
Common scenarios include:
- Downloading a previously generated speech synthesis audio file for further processing or playback.
- Archiving or backing up audio history items.
- Integrating historical audio retrieval into automated pipelines for content management or review.
For example, a user might automate fetching an audio clip by its history ID and then send it as an attachment in an email or upload it to a media server.
Properties
| Name | Meaning |
|---|---|
| History Item ID | The unique identifier of the history item whose audio you want to retrieve. This is required. |
| Binary Name | (Optional) Customize the name of the binary output field where the audio data will be stored. Defaults to "data". |
| File Name | (Optional) Specify the filename for the output audio file. Defaults to "voice". |
Additionally, there is a notice property informing users that this node is currently in beta and under active development, with links for more information and support.
Output
The node outputs the audio data of the specified history item in binary form. The binary data represents the audio file retrieved from the ElevenLabs service.
- The binary data is accessible under the key defined by the "Binary Name" property (default:
data). - The file name of the binary data can be customized via the "File Name" property (default:
voice).
The JSON output typically contains metadata about the operation but primarily serves as a container for the binary audio data.
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. - Proper configuration of the API key credential within n8n is necessary for successful operation.
Troubleshooting
- Invalid or missing History Item ID: If the provided history item ID does not exist or is incorrect, the node may return an error or empty response. Verify the ID is correct and corresponds to an existing history item.
- Authentication errors: Ensure the API key credential is valid and has the necessary permissions.
- Network issues: Connectivity problems can cause request failures; check network access to the ElevenLabs API.
- Beta status caveats: Since the node is marked as beta and under active development, some features or responses might change or behave unexpectedly. Refer to the linked resources for updates and support.