Get History
Retrieves the generation history from your ElevenLabs account, showing all previously generated audio items.
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.
- Page Size (String) - Maximum number of history items to return per page (default: 100, max: 1000).
Options
- Last History Item ID (String) - Optional ID of the last history item for pagination. Use this to retrieve the next page of results.
- API Key - Your ElevenLabs AI API key. Optional if using Connection ID.
Outputs
- History (Object) - List of history items, each containing:
- history_item_id - Unique identifier for the generation
- text - The text that was converted to speech
- voice_id - ID of the voice used
- voice_name - Name of the voice used
- model_id - Model used for generation
- date_unix - Timestamp of generation
- character_count_change_from - Characters before generation
- character_count_change_to - Characters after generation
- content_type - Audio content type
- state - Generation state (e.g., completed)
How It Works
The Get History node retrieves your generation history. When executed, the node:
- Validates that page size is a valid integer
- Either uses the provided connection or creates a new client with direct API key
- Calls the ElevenLabs API to retrieve history items
- Handles pagination automatically if there are more items
- Returns the complete list of history items
Requirements
- Valid ElevenLabs API key (via Connect node or direct option)
- Page size must be a valid integer between 1 and 1000
Error Handling
The node will return specific errors in the following cases:
- Invalid page size - "Page Size must be a valid integer between 1 and 1000."
- Retrieval failure - "Failed to retrieve history: [error details]"
Usage Notes
- Returns history from most recent to oldest
- Use pagination for large histories to avoid timeouts
- The Last History Item ID enables retrieving subsequent pages
- History includes both successful and failed generations
- Character count shows usage for billing tracking
- History items can be used to download previously generated audio
- The node automatically handles pagination if needed
- Use the history_item_id with Get History Item or Get Audio from History Item nodes
Example Use Cases
- Auditing past audio generations
- Tracking character usage for billing
- Finding previously generated audio files
- Building reports on voice usage
- Retrieving old generations without regenerating
- Analyzing which voices were used most
- Checking generation success rates
- Managing and cleaning up old generations