Actions13
- Speech Actions
- Voice Actions
- History Actions
- User Actions
Overview
The "Get History" operation of the ElevenLabs node retrieves a list of history items related to previous interactions or actions performed via the ElevenLabs API. This is useful for auditing, reviewing past requests, or implementing pagination over historical data.
Typical use cases include:
- Fetching recent voice synthesis or speech generation history.
- Paginating through large sets of history records to analyze usage patterns.
- Integrating with dashboards or logs that display user activity or system events.
For example, you might use this node to fetch the last 100 speech synthesis requests made by your application to monitor usage or debug issues.
Properties
| Name | Meaning |
|---|---|
| Page Size | How many history items to return at maximum. Cannot exceed 1000. |
| Last Item ID | After which history item ID to start fetching. Used for paginating across a large collection of history items. |
| Voice ID | The voice to filter the history by. Can be selected from a searchable list of available voices or entered manually by ID. |
Additionally, there is a notice property displayed as an informational message about the node being in beta and under active development, with links for more information and support.
Output
The node outputs JSON data containing the retrieved history items. Each item typically includes details such as the unique ID, timestamp, associated voice (if filtered), and other metadata relevant to the history record.
If binary data is involved (e.g., audio files linked to history entries), it would be represented accordingly, but based on the provided code and properties, the primary output is structured JSON representing history records.
Dependencies
- Requires an API key credential for authenticating with the ElevenLabs API.
- The node makes HTTP POST requests to
https://api.elevenlabs.io/v1. - No additional external dependencies are indicated beyond the ElevenLabs API access.
Troubleshooting
Common Issues:
- Exceeding the maximum allowed page size (over 1000) will likely cause errors.
- Providing an invalid or expired API key will result in authentication failures.
- Using an incorrect or non-existent Last Item ID may lead to empty results or errors.
- Selecting a Voice ID that does not exist or is not accessible with the current credentials may cause filtering to fail.
Error Messages:
- Authentication errors: Check that the API key credential is correctly configured and valid.
- Validation errors on parameters: Ensure
page_sizeis within allowed limits and IDs are correctly formatted. - Network or API errors: Verify network connectivity and that the ElevenLabs API service is operational.