Actions16
Overview
The node integrates with the ElevenLabs API, focusing here on the History resource and specifically the Get History Audio operation. This operation retrieves audio data associated with a specific history item ID from ElevenLabs' service.
This node is useful when you want to programmatically access previously generated or stored audio clips linked to your ElevenLabs account history. For example, you might use it to fetch and reuse voice recordings created earlier without regenerating them, enabling workflows that involve audio playback, processing, or archival.
Practical scenarios include:
- Retrieving a past text-to-speech conversion audio file for further processing.
- Accessing user history audio clips for review or analysis.
- Automating download and storage of historical audio assets.
Properties
| Name | Meaning |
|---|---|
| History Item ID | The unique identifier of the history item whose 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 output audio file. Defaults to "voice". |
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 the retrieved audio as binary data. The binary data represents the audio content of the specified history item.
- The binary data key defaults to
"data"but can be customized via the Binary Name property. - The output file name defaults to
"voice"but can be changed using the File Name property. - The JSON output will typically contain metadata about the operation or the history item, but the main payload is the binary audio data.
Dependencies
- Requires an API key credential for ElevenLabs API authentication.
- The node makes HTTP POST requests to
https://api.elevenlabs.io/v1. - No additional external dependencies are indicated beyond the ElevenLabs API.
Troubleshooting
- Missing or invalid History Item ID: The node requires a valid history item ID; ensure this is correctly provided.
- Authentication errors: Ensure the API key credential is correctly configured and has necessary permissions.
- Network issues: Verify network connectivity to the ElevenLabs API endpoint.
- Beta status warnings: Since the node is in beta, some features may be unstable or subject to change. Check the provided links for updates or known issues.
Common error messages would likely relate to invalid IDs, unauthorized access, or network timeouts. Resolving these involves verifying input parameters, credentials, and network conditions.