Actions20
Overview
This node integrates with the Tavus API to manage AI-driven video content. Specifically, the Video - Get operation retrieves detailed information about a single video by its unique ID. This is useful when you want to fetch metadata or status of a previously created video, for example, to check if the video generation is complete or to obtain URLs for playback or thumbnails.
Common scenarios include:
- Fetching video details after creation to display or process further.
- Checking video processing status in an automation workflow.
- Retrieving additional video data such as thumbnails when verbose mode is enabled.
Properties
| Name | Meaning |
|---|---|
| Video ID | The unique identifier of the video you want to retrieve. |
| Additional Fields | Options to include extra data; currently supports: Verbose (boolean) to get thumbnails and other extended info. |
Output
The output JSON contains the video object returned from the Tavus API for the specified video ID. If the "Verbose" option is enabled, the response includes additional video data such as thumbnails.
The structure typically includes fields like:
- Video metadata (e.g., ID, name, creation date)
- Status of the video generation
- URLs for video playback or download
- Thumbnails and other media assets (if verbose is true)
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Tavus API using a valid API authentication token configured in n8n credentials.
- Network access to Tavus API endpoints.
Troubleshooting
- Invalid Video ID: If the provided video ID does not exist or is malformed, the API will likely return an error. Verify the ID correctness.
- API Authentication Errors: Ensure that the API key credential is correctly set up and has sufficient permissions.
- Verbose Option Misuse: The verbose field must be boolean; invalid values may cause request failures.
- Network Issues: Connectivity problems can cause timeouts or failed requests.
If errors occur, check the error message returned by the node for clues, and verify all input parameters and credentials.
Links and References
- Tavus API Documentation (general reference for API endpoints and data structures)
- n8n documentation on creating custom nodes