Actions16
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 reuse, analysis, or redistribution of past audio outputs.
Common scenarios include:
- Fetching a previously generated speech synthesis audio clip for playback or further processing.
- Archiving or backing up audio files created during earlier workflow executions.
- Integrating historical audio content into new automation sequences without regenerating it.
For example, a user might automate a podcast production pipeline where they generate voiceovers and later retrieve those audio files from history to combine with other media elements.
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 property where the audio data will be stored. Default is "data". |
| File Name | (Optional) Specify the filename for the output audio file. Default is "voice". |
Additionally, the node displays a notice indicating it is currently in beta and under active development, with links for more information and support.
Output
The node outputs the retrieved audio as binary data attached to the binary property of the output item. The binary data represents the audio file corresponding to the specified history item.
- The binary data key defaults to
"data"but can be customized via the "Binary Name" property. - The filename of the binary data can be set using the "File Name" property; otherwise, it defaults to
"voice".
No additional JSON fields are explicitly described for this operation's output beyond the binary audio content.
Dependencies
- Requires an API authentication token credential for ElevenLabs API access.
- The node makes HTTP POST requests to the ElevenLabs API endpoint at
https://api.elevenlabs.io/v1. - No other external dependencies are indicated.
Troubleshooting
- Invalid or missing History Item ID: The node requires a valid history item ID. If omitted or incorrect, the API call will fail. Ensure the ID corresponds to an existing history record.
- Authentication errors: If the API key credential is invalid or missing, the node will not authenticate successfully. Verify the API key is correctly configured.
- Beta status caveats: As the node is marked beta and under active development, some features may be unstable or incomplete. Check the provided support links for updates or known issues.
- Binary output handling: If downstream nodes do not handle binary data properly, the audio file may not be accessible. Confirm subsequent nodes support binary inputs.