Skip to main content

Get Audio from History Item

Downloads the audio file from a previously generated history item and saves it to disk.

Common Properties

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.

Inputs

  • Connection Id (String) - Connection ID from the Connect node. Optional if you provide API Key directly.
  • History Item ID (String) - ID of the history item to download audio from.
  • Save Path (String) - File path where the audio will be saved (e.g., "downloads/audio.mp3").

Options

  • API Key - Your ElevenLabs AI API key. Optional if using Connection ID.

Outputs

This node does not have outputs. The audio file is saved to the specified path.

How It Works

The Get Audio from History Item node retrieves and saves audio. When executed, the node:

  1. Validates that save path and history item ID are provided
  2. Either uses the provided connection or creates a new client with direct API key
  3. Calls the ElevenLabs API to retrieve the audio
  4. Streams the audio chunks to the specified file path
  5. Saves the complete audio file to disk

Requirements

  • Valid ElevenLabs API key (via Connect node or direct option)
  • Valid history item ID
  • Writable file path for saving audio
  • The history item must have completed successfully

Error Handling

The node will return specific errors in the following cases:

  • Missing save path - "Save Path cannot be empty. Please provide a valid file path for saving the audio."
  • Missing history item ID - "History Item ID cannot be empty. Please provide a valid history item ID."
  • Permission error - "Permission denied when writing to: [path]. Please check file permissions."
  • Retrieval failure - "Failed to retrieve audio from history item: [error details]"

Usage Notes

  • Retrieves previously generated audio without regenerating
  • Saves character quota by reusing existing generations
  • Audio format matches the original generation (typically MP3)
  • The save path directory must exist before running
  • Useful for downloading audio generated in previous sessions
  • History item IDs come from the Get History node
  • Audio is streamed in chunks, making it memory-efficient
  • Make sure the history item generation completed successfully
  • Failed generations won't have audio available

Example Use Cases

  • Downloading audio from previous sessions without regenerating
  • Archiving generated audio files
  • Retrieving audio generated by other team members
  • Building audio libraries from history
  • Saving character quota by reusing generations
  • Batch downloading multiple historical generations
  • Recovering audio from old generations
  • Creating backups of generated audio