ElevenLabs icon

ElevenLabs

WIP

History → Get History

AI-generated

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 by specifying the last retrieved item ID.
  • Filtering history by voice ID to see usage or results related to a specific voice.

For example, you might use this node to display the last 100 text-to-speech conversions made with a particular voice or to build a UI that allows users to browse their past audio generation requests.

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 paginating through large collections.
Voice ID The voice to filter history by. Can be selected from a searchable list of available voices or entered as an ID string.

Note: There is also a notice property informing users that the node is in beta and under active development, with links for more information and support.

Output

The output contains a JSON array of history items fetched from the ElevenLabs API. Each item represents a single historical record related to speech or voice operations. The exact structure depends on the API response but typically includes identifiers, timestamps, associated voice IDs, and metadata about the request or result.

If binary data is returned (e.g., audio files), it would represent the generated speech or voice content corresponding to the history entries, but this operation primarily focuses on metadata retrieval.

Dependencies

  • Requires an API key credential for ElevenLabs API authentication.
  • Depends on network access to https://api.elevenlabs.io/v1.
  • No additional environment variables are explicitly required beyond the API key.
  • The node uses internal methods to list voices for selection when filtering by Voice ID.

Troubleshooting

  • Common issues:

    • Exceeding the maximum allowed page size (over 1000) will likely cause errors.
    • Providing an invalid or non-existent Last Item ID may result in empty responses or errors.
    • Using an incorrect Voice ID (not matching any existing voice) may yield no results.
    • Network or authentication failures due to missing or invalid API keys.
  • Error messages:

    • Authentication errors indicate problems with the provided API key; verify and update credentials.
    • Pagination errors suggest invalid Last Item ID or exceeding page size limits; adjust parameters accordingly.
    • Empty results may mean no history exists for the given filters; try broadening criteria.

Links and References

Discussion