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 tasks, specifically focusing on lipsync videos in this context. The "Get" operation for the "Lipsync" resource retrieves detailed information about a specific lipsync request using its unique identifier. This is useful when you want to check the status or details of a previously created lipsync video.

Common scenarios:

  • Monitoring the progress or result of a lipsync video generation.
  • Retrieving metadata or output URLs related to a specific lipsync job.
  • Integrating lipsync video status checks into automated workflows.

Practical example:
You have initiated a lipsync video creation and received a lipsync ID. Using this node's "Get" operation, you can fetch the current state and details of that lipsync video to decide whether to proceed with further processing or notify users.

Properties

Name Meaning
Lipsync ID A unique identifier for the lipsync request. This is required to fetch the specific lipsync video details.

Output

The node outputs JSON data representing the lipsync video details retrieved from the Tavus API. This typically includes metadata such as status, URLs to the generated video, timestamps, and other relevant information about the lipsync request.

If the API provides binary data (e.g., video files), it would be handled separately, but based on the code, the output here is JSON metadata only.

Dependencies

  • Requires an active connection to the Tavus API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The node uses internal helper functions to make HTTP requests to the Tavus API endpoints.

Troubleshooting

  • Invalid Lipsync ID: If the provided Lipsync ID does not exist or is malformed, the API will likely return an error. Ensure the ID is correct and corresponds to an existing lipsync request.
  • Authentication errors: Missing or invalid API credentials will cause authorization failures. Verify that the API key or token is correctly set up in n8n.
  • Network issues: Connectivity problems may prevent the node from reaching the Tavus API. Check network settings and firewall rules.
  • JSON parsing errors: Although unlikely in this operation, if any JSON input is malformed, errors may occur. For this "Get" operation, no complex JSON inputs are expected.

Links and References

Discussion