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 content. Specifically, the "Video" resource with the "Get Many" operation allows users to retrieve multiple video records from their Tavus account. This is useful for scenarios where you want to list or process batches of videos, such as displaying all generated videos, syncing video metadata, or performing bulk operations on video data.

For example, a marketing team could use this node to fetch all videos created by their AI system to update a content management system or trigger further workflows based on video availability.

Properties

Name Meaning
Return All Whether to return all available videos or limit the number of results returned.
Limit The maximum number of video results to return if not returning all. Range: 1 to 100.

Output

The node outputs an array of JSON objects representing videos retrieved from the Tavus API. Each object contains video details as provided by the API, such as video IDs, scripts, replica references, and other metadata.

  • The output is structured as a JSON array under the json field.
  • No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Tavus API.
  • The node uses internal helper functions to make HTTP requests to the Tavus API endpoints.
  • No additional external dependencies are required beyond the configured API authentication.

Troubleshooting

  • Common issues:

    • Exceeding API rate limits when requesting all videos (Return All set to true).
    • Providing invalid values for Limit (must be between 1 and 100).
    • Network or authentication errors due to missing or incorrect API credentials.

  • Error messages:

    • Errors related to invalid parameters will typically indicate which property is incorrect.
    • Authentication failures will result in errors indicating unauthorized access; ensure the API key credential is correctly configured.
    • If the node throws an error about JSON parsing, it may relate to other operations but not this one specifically.

Links and References

Discussion