ElevenLabs icon

ElevenLabs

WIP
Join our community

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 paginating through historical data to analyze usage patterns or debug issues.

Typical use cases include:

  • Fetching recent voice synthesis or speech generation history.
  • Paginating through large sets of history records to process or display them incrementally.
  • Filtering history by voice ID to see usage or results specific to a particular voice.

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 to filter history by. Can be selected from a searchable list of voices or entered as an ID.

Additionally, there is a notice property displayed in the node UI informing users that this node is currently in BETA and under active development, with links for more information and support.

Output

The output contains a JSON array of history items retrieved from the ElevenLabs API. Each item represents a single historical record 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 or result.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for ElevenLabs API authentication.
  • Makes HTTP POST requests to https://api.elevenlabs.io/v1.
  • The node relies on the ElevenLabs API being available and accessible.
  • No additional environment variables are explicitly required beyond the API key.

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 history item ID may cause empty results or errors.
    • Network connectivity issues can prevent successful API calls.

  • Error Messages:

    • Authentication errors: Check that the API key credential is correctly configured and valid.
    • Pagination errors: Ensure the last item ID used for pagination exists and is correct.
    • Rate limiting or quota exceeded: Respect API limits and retry after some time if needed.

Links and References

Discussion