ElevenLabs icon

ElevenLabs

WIP

History → Delete History Item

AI-generated

Overview

The node provides integration with the ElevenLabs API, focusing on various resources including Speech, Voice, History, and User. Specifically, for the History resource with the Delete History Item operation, the node allows users to delete a specific history item by its ID. This is useful in scenarios where you want to manage or clean up historical data related to speech synthesis or voice generation activities tracked by ElevenLabs.

Practical examples include:

  • Removing outdated or incorrect entries from your speech synthesis history.
  • Automating cleanup of history items after processing them elsewhere.
  • Managing user-specific history logs programmatically within an n8n workflow.

Properties

Name Meaning
This node is currently in BETA and under active development.
Visit this page for more information or contact the n8Ninja on X.

To support my work, please share this youtube video 🥷🙏
Informational notice about the node's beta status and links for support and updates.
History Item ID The unique identifier of the history item that you want to delete. This is a required string input.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide error details if it failed. The exact structure depends on the ElevenLabs API response but generally includes status information.

There is no indication that the node outputs binary data for this operation.

Dependencies

  • Requires an API key credential for ElevenLabs API authentication.
  • The node makes HTTP POST requests to https://api.elevenlabs.io/v1.
  • Proper configuration of the ElevenLabs API key in n8n credentials is necessary.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent History Item ID will likely cause the API to return an error.
    • Missing or incorrect API credentials will prevent the node from authenticating successfully.
    • Network connectivity issues can cause request failures.
  • Error messages:

    • Errors related to authorization typically indicate missing or invalid API keys; ensure the correct API key is configured.
    • "History item not found" or similar errors suggest the provided History Item ID does not exist; verify the ID before running.
    • Timeout or network errors require checking internet connection or API availability.

Links and References

Discussion