ElevenLabs icon

ElevenLabs

WIP

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 usage tracked by ElevenLabs.

Practical examples include:

  • Removing outdated or incorrect entries from your speech generation history.
  • Automating cleanup of history items after processing them elsewhere.
  • Managing user-specific history data 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.

Since this operation deals with deleting a history item, no binary data output is expected.

Dependencies

  • Requires an API key credential for ElevenLabs API authentication.
  • The node makes HTTP POST requests to https://api.elevenlabs.io/v1.
  • No additional external dependencies are indicated.

Troubleshooting

  • Common issues:

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

    • Errors related to authorization typically indicate problems with the API key; ensure it is correctly configured.
    • "History item not found" or similar errors suggest the provided ID does not exist; verify the ID before running the node.
    • General HTTP errors (e.g., 500) may require retrying or checking ElevenLabs service status.

Links and References

Discussion