Eleven Labs Conversational icon

Eleven Labs Conversational

Interact with ElevenLabs Conversational AI API

Conversation → Delete

AI-generated

Overview

The node provides integration with the ElevenLabs Conversational AI API, enabling interaction with various resources such as agents, conversations, voices, knowledge bases, and phone calls. Specifically, for the Conversation - Delete operation, it allows users to delete a conversation by specifying its unique ID. This is useful in scenarios where you want to programmatically remove conversation records, for example, to manage storage, comply with data retention policies, or clean up test data.

Practical example:

  • Automatically deleting conversations older than a certain date to maintain privacy compliance.
  • Removing conversations that were created during testing or debugging phases.

Properties

Name Meaning
Conversation ID The unique identifier of the conversation to delete. This is required to specify which conversation should be removed.

Output

The output of the delete operation typically contains a JSON object indicating the result of the deletion request. While the exact structure is not detailed in the provided code, usually such an operation returns either a success confirmation or details about the deleted conversation.

No binary data output is expected from this operation.

Dependencies

  • Requires an active connection to the ElevenLabs Conversational AI API.
  • Requires an API key credential configured in n8n to authenticate requests to ElevenLabs.
  • The node depends on internal services (ConversationService) to perform the delete operation.

Troubleshooting

  • Common issues:

    • Invalid or missing Conversation ID: The operation requires a valid conversation ID; providing an empty or incorrect ID will cause failure.
    • Authentication errors: If the API key is invalid or missing, the node will fail to connect to the ElevenLabs API.
    • Network issues: Connectivity problems can prevent successful API calls.
  • Error messages:

    • "Conversation ID is required" or similar validation errors indicate missing input.
    • API error responses may include HTTP status codes like 401 (Unauthorized) or 404 (Not Found) if the conversation does not exist.
  • Resolutions:

    • Ensure the Conversation ID is correctly set and corresponds to an existing conversation.
    • Verify that the API key credential is properly configured and has necessary permissions.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion