Actions13
- Speech Actions
- Voice Actions
- History Actions
- User Actions
Overview
The "Get History" operation of the ElevenLabs node allows users to retrieve a list of previously generated speech synthesis history items from their ElevenLabs account. This is useful for auditing, reviewing past text-to-speech conversions, or managing and analyzing usage over time. For example, a user might want to fetch recent speech generation records to display in a dashboard or to re-use audio outputs without regenerating them.
Properties
| Name | Meaning |
|---|---|
| Page Size | Maximum number of history items to return (up to 1000). Controls pagination size. |
| Last Item ID | The ID after which to start fetching history items. Used for paginating through large collections. |
| Voice ID | Selects a specific voice to filter the history by. Can be chosen from a searchable list or entered as an ID. |
Additionally, there is an informational notice property:
| Name | Meaning |
|---|---|
| API Key Notice | A notice reminding users that an API key from ElevenLabs is required to use this node, with a link to obtain it. |
Output
The output json field contains an array of history items representing previous speech synthesis requests. Each item typically includes metadata such as the text input, voice used, timestamps, and possibly identifiers for the generated audio. This allows downstream nodes or workflows to process or analyze past speech generation data.
If binary data is included (not explicitly shown here), it would represent audio files or related media generated during those history entries.
Dependencies
- Requires an API key credential from ElevenLabs to authenticate API requests.
- Relies on the ElevenLabs REST API endpoint at
https://api.elevenlabs.io/v1. - The node uses HTTP POST requests with JSON content type headers.
- No other external dependencies are indicated.
Troubleshooting
Common Issues:
- Exceeding the maximum allowed page size (over 1000) may cause errors or truncated results.
- Providing an invalid or expired API key will result in authentication failures.
- Incorrect or non-existent
last_history_item_idvalues may lead to empty or incomplete pagination results. - Specifying a
voice_idthat does not exist or is inaccessible to the user may yield no matching history items.
Error Messages:
- Authentication errors typically indicate missing or invalid API keys; ensure the correct key is configured.
- Validation errors may occur if parameters like
page_sizeexceed limits or have wrong types. - Network or API downtime errors should be retried later or checked against ElevenLabs service status.
Links and References
- ElevenLabs Dashboard – Obtain your API key.
- ElevenLabs API Documentation (general reference, not linked in code but recommended to consult for detailed API behavior).