TavusInstall

Overview

This node interacts with the Tavus API to manage conversations involving AI-driven replicas and personas. Specifically, the Conversation - List operation retrieves a paginated list of conversations, optionally filtered by their status (active or ended). This is useful for scenarios where you want to monitor ongoing or past conversations, analyze conversation history, or integrate conversation data into workflows.

Practical examples include:

• Fetching active conversations to display in a dashboard.
• Retrieving ended conversations for archival or reporting purposes.
• Paginating through large sets of conversations to process them in batches.

Properties

Output

The output is a JSON array where each item represents a conversation object as returned by the Tavus API. Each conversation object typically includes details such as conversation ID, participants, status, timestamps, and other metadata related to the conversation.

No binary data is output by this operation.

Dependencies

• Requires an API key credential for authenticating with the Tavus API.
• The node uses HTTP requests to the Tavus API endpoints.
• No additional environment variables are required beyond the API authentication setup.

Troubleshooting

• Invalid JSON in properties: If you extend functionality with custom JSON properties (not applicable here but relevant in other operations), ensure JSON is valid to avoid errors.
• API request failures: Common issues include invalid API keys, network connectivity problems, or exceeding rate limits. Verify your API credentials and network access.
• Pagination parameters: Providing a page number less than 1 or a limit outside the allowed range (1-100) may cause errors or unexpected results. Always use valid values.
• Empty results: If filtering by status, ensure that conversations exist with that status; otherwise, the result will be empty.

Links and References

• Tavus API Documentation (for detailed API endpoint info)
• n8n documentation on creating custom nodes