Tavus icon

Tavus

Work with Tavus API for AI-driven video generation
Join our community

Actions20

Overview

This node integrates with the Tavus API to manage AI-driven video generation and related conversational AI resources. Specifically, for the Conversation - Get operation, it retrieves detailed information about a single conversation by its unique identifier. This is useful when you want to fetch the current state or details of a specific conversation, such as participants, messages, status, or metadata.

Common scenarios include:

  • Monitoring or auditing conversations in an AI-driven chat or video interaction system.
  • Fetching conversation details to display in dashboards or logs.
  • Integrating conversation data into workflows that depend on conversation context or history.

Example: You have a conversation ID from a previous step or event, and you want to retrieve all details about that conversation to decide the next action in your workflow.

Properties

Name Meaning
Conversation ID The unique identifier for the conversation you want to retrieve.

Output

The output is a JSON object representing the conversation details returned by the Tavus API. It typically includes fields such as conversation metadata, participants, messages, status, timestamps, and any other relevant conversation data provided by the API.

The node does not explicitly handle binary data for this operation.

Example output structure (simplified):

{
  "id": "string",
  "status": "active" | "ended",
  "participants": [
    {
      "replica_id": "string",
      "persona_id": "string",
      ...
    }
  ],
  "messages": [
    {
      "sender": "string",
      "text": "string",
      "timestamp": "string"
    }
  ],
  "created_at": "string",
  "updated_at": "string",
  ...
}

Dependencies

  • Requires an active connection to the Tavus API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • No additional environment variables are required beyond the API credential setup.

Troubleshooting

  • Invalid Conversation ID: If the conversation ID is incorrect or does not exist, the API will likely return a 404 error. Verify the ID before making the request.
  • Authentication Errors: Ensure the API key or token is valid and has permissions to access conversation data.
  • Network Issues: Connectivity problems can cause request failures; check network settings and Tavus API availability.
  • JSON Parsing Errors: Not applicable here since the input is a simple string ID, but if extended properties were used, ensure JSON inputs are valid.

If the node throws errors related to invalid JSON, it usually pertains to other operations where JSON input is expected (not relevant for this get operation).

Links and References

Discussion