Actions16
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 previous interactions or generated content within the ElevenLabs platform.
Practical examples include:
- Removing outdated or incorrect speech synthesis history entries.
- Managing storage by deleting unnecessary history items programmatically.
- Automating cleanup tasks as part of a larger workflow involving ElevenLabs services.
Properties
| Name | Meaning |
|---|---|
| History Item ID | The unique identifier of the history item to be deleted. This is a required string input. |
Additionally, there is a notice property displayed in the node UI indicating that the node is currently in beta and under active development, with links for more information and support.
Output
The node outputs JSON data representing the result of the delete operation. Typically, this would include confirmation of deletion or any relevant status messages returned by the ElevenLabs API.
If the node supports binary data output (not indicated here), it would relate to any media or files associated with the history item, but for the delete operation, the output is primarily JSON confirming the action.
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 beyond the ElevenLabs API access.
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 successful communication with the ElevenLabs API.
- Network connectivity issues can cause request failures.
Error messages:
- Errors related to authorization typically indicate problems with the API key; ensure the correct key is configured.
- "History item not found" or similar errors suggest the provided ID does not exist; verify the ID before attempting deletion.
- General HTTP errors (e.g., 4xx or 5xx) should be checked against the ElevenLabs API documentation for specific meanings.
Links and References
- ElevenLabs API Documentation (general reference)
- Beta notice links provided in the node UI: