Actions20
Overview
This node integrates with the Tavus API to create a lipsync video by synchronizing a given original video with a new source audio track. It is useful for scenarios where you want to replace or dub the audio of an existing video while keeping the original visuals intact, such as creating localized versions of videos, dubbing voiceovers, or generating AI-driven lip-synced content.
For example, you can provide a publicly accessible URL to an original MP4 video and a separate MP3 or WAV audio file. The node sends these inputs to the Tavus API, which processes and returns a new lipsync video that matches the new audio with the original video’s lip movements.
Properties
| Name | Meaning |
|---|---|
| Original Video URL | Publicly accessible URL to the original video file in MP4 format. |
| Source Audio URL | Publicly accessible URL to the source audio file in MP3 or WAV format. |
| Callback URL | (Optional) URL to receive a notification callback when the lipsync video processing completes. |
| Lipsync Name | (Optional) A custom name to assign to the generated lipsync video. |
Output
The node outputs JSON data representing the response from the Tavus API after creating the lipsync video. This typically includes metadata about the lipsync request such as its unique identifier, status, and possibly URLs to access the generated video once ready.
The node does not output binary data directly; instead, it provides references (URLs or IDs) to the processed lipsync video managed by the Tavus service.
Dependencies
- Requires an active Tavus API key credential configured in n8n to authenticate requests.
- Depends on the Tavus API service being accessible over the internet.
- Input URLs for the original video and source audio must be publicly accessible so the Tavus API can fetch them.
Troubleshooting
- Invalid or inaccessible URLs: Ensure that the provided original video and source audio URLs are publicly accessible without authentication and correctly point to valid media files (.mp4 for video, .mp3/.wav for audio).
- API authentication errors: Verify that the Tavus API key credential is correctly set up in n8n and has sufficient permissions.
- JSON parsing errors: If optional properties like callback URL or lipsync name are malformed or contain invalid characters, the API might reject the request.
- Callback URL issues: If using a callback URL, ensure the endpoint is reachable and properly handles incoming webhook notifications.
- Rate limits or quota exceeded: The Tavus API may enforce usage limits; check your account status if requests fail repeatedly.
Links and References
- Tavus API Documentation (for detailed API capabilities and parameters)
- n8n Documentation (for general guidance on using credentials and HTTP request nodes)