Actions20
Overview
This node integrates with the Tavus API to manage AI-driven video generation and related conversational AI features. Specifically, for the Conversation - Delete operation, it allows users to delete a conversation by its unique identifier. This is useful in scenarios where conversations are no longer needed or must be removed for privacy or data management reasons.
Practical examples include:
- Automatically cleaning up old or inactive conversations from your system.
- Removing test or demo conversations after validation.
- Managing conversation lifecycle by deleting ended or obsolete conversations programmatically.
Properties
| Name | Meaning |
|---|---|
| Conversation ID | The unique identifier for the conversation to delete. |
Output
The output JSON contains the response from the Tavus API after attempting to delete the specified conversation. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
The structure depends on the API but generally includes status information about the deletion request.
No binary data is output by this operation.
Dependencies
- Requires an active connection to the Tavus API.
- Requires an API authentication token configured in n8n credentials (referred generically as "an API key credential").
- Network access to Tavus API endpoints.
Troubleshooting
Common issues:
- Invalid or missing Conversation ID: The node requires a valid conversation ID; ensure this is correctly provided.
- Authentication errors: Ensure the API key credential is valid and has permissions to delete conversations.
- Network or API downtime: Check network connectivity and Tavus service status.
Common error messages:
"Properties must be valid JSON": Not applicable here since no JSON properties are required for delete, but relevant for other operations.- API error responses indicating conversation not found or unauthorized access. Verify the conversation ID and credentials.
To resolve errors:
- Double-check the Conversation ID input.
- Confirm API credentials are correct and have necessary permissions.
- Review API documentation or contact Tavus support if persistent errors occur.
Links and References
- Tavus API Documentation (generic link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- General REST API best practices for error handling and authentication.