Actions16
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 and display them in an admin panel.
Properties
| Name | Meaning |
|---|---|
| Page Size | Maximum number of history items to return (up to 1000). Controls the size of each page of results. |
| Last Item ID | The ID after which to start fetching history items. Used for pagination to continue from a specific point. |
| Voice ID | The voice identifier to filter history items by a specific voice. Can be selected from a list or entered manually. |
Additionally, there is a notice property displayed as informational text about the node being in beta and under active development, with links for more information and support.
Output
The output JSON contains an array of history items fetched from the ElevenLabs API. Each item represents a record of a past action or event related to speech or voice operations. The exact structure of each history item depends on the API response but typically includes identifiers, timestamps, and metadata about the request.
If binary data is returned (e.g., audio files), it would represent the actual media content associated with a history entry, such as generated speech audio.
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 by the API key can cause filtering to fail.
Error messages:
- Authentication errors usually indicate problems with the API key; verify credentials.
- Pagination errors may occur if the Last Item ID is malformed or not found; ensure correct IDs are used.
- Rate limiting or quota exceeded errors may arise if too many requests are made in a short time; implement retries or backoff.