Actions13
- Speech Actions
- Voice Actions
- History Actions
- User Actions
Overview
The Get History Audio operation for the "History" resource in this custom n8n node allows users to retrieve audio files associated with a specific history item from the ElevenLabs API. This is particularly useful for workflows that need to access, download, or process previously generated speech/audio content. For example, you might use this node to fetch an audio file for archival, playback, or further processing after it has been created by another part of your automation.
Properties
| Display Name | Type | Description |
|---|---|---|
| Notice | notice | Informational message about the node's beta status, support links, and latest updates. |
| History Item ID | string | The unique identifier of the history item whose audio you want to retrieve. (Required) |
| Additional Fields | collection | Optional settings: |
| - Binary Name | string | Change the output binary property name (default: data). |
| - File Name | string | Change the output file name (default: voice). |
Output
- Binary Data:
The node outputs the retrieved audio as a binary property.- The property name can be customized via "Binary Name" (default:
data). - The file name can be set via "File Name" (default:
voice).
- The property name can be customized via "Binary Name" (default:
- JSON Output:
The JSON output will include metadata about the operation and may reference the binary data property.
Dependencies
- External Service: Requires access to the ElevenLabs API.
- API Key: You must configure valid ElevenLabs API credentials in n8n under the credential type
elevenLabsApi.
Troubleshooting
- Missing or Invalid History Item ID:
If the "History Item ID" is missing or incorrect, the node may return an error indicating that the item was not found. Double-check the ID value. - Authentication Errors:
If your API key is missing or invalid, you may receive authentication errors. Ensure your ElevenLabs API credentials are correctly configured in n8n. - Binary Output Issues:
If you change the "Binary Name" or "File Name" fields, ensure downstream nodes reference the correct property names.