Actions20
Overview
The node integrates with the Tavus API to manage AI-driven video generation and related conversational AI features. Specifically, for the Conversation - End operation, it allows users to end an ongoing conversation by its unique identifier. This is useful in scenarios where a conversation session needs to be programmatically terminated, such as after completing an interaction or when cleaning up resources.
Practical examples include:
- Automatically ending a customer support chatbot conversation once the issue is resolved.
- Closing a conversational session in an AI-driven video or replica interaction workflow.
- Managing lifecycle of conversations in automated workflows that involve multiple AI personas or replicas.
Properties
| Name | Meaning |
|---|---|
| Conversation ID | The unique identifier for the conversation to be ended. Required to specify which conversation to close. |
Output
The node outputs JSON data representing the response from the Tavus API after attempting to end the specified conversation. This typically includes confirmation of the conversation's termination status or any relevant metadata returned by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Tavus API via an API key credential configured in n8n.
- The node depends on the
tavusApiRequesthelper function to make authenticated HTTP requests to the Tavus API endpoints. - Proper network access to the Tavus API endpoint is necessary.
Troubleshooting
- Invalid Conversation ID: If the provided conversation ID does not exist or is malformed, the API may return an error indicating the conversation was not found. Verify the ID correctness.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly set up in n8n.
- API Rate Limits or Downtime: If the Tavus API service is unavailable or rate limits are exceeded, requests may fail. Check Tavus service status and retry later.
- JSON Parsing Errors: Although not directly applicable to the "end" operation, other operations involving JSON input fields require valid JSON syntax; otherwise, errors will be thrown.
Links and References
- Tavus API Documentation (general reference for API endpoints and usage)
- n8n documentation on Creating Custom Nodes