Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node provides various ffmpeg-related video processing functionalities within n8n. Specifically, for the "Video Processing" resource and the "Combine Audio To Video" operation, it allows users to merge an audio track with a video file. This is useful when you have separate audio and video sources and want to produce a single combined media file.
Common scenarios include:
- Adding background music or narration to a silent video.
- Replacing the original audio track of a video with a different audio source.
- Combining externally sourced audio (e.g., voiceover) with video footage.
Example: You have a recorded video without sound and a separate audio commentary file. Using this node, you can combine them into one video file with synchronized audio.
Properties
| Name | Meaning |
|---|---|
| Video Input | A valid video URL or the name of the input binary field containing the video file. |
| Audio Input | A valid audio URL or the name of the input binary field containing the audio file. |
| Video Output Name | The name of the output binary field where the combined video file will be stored. |
Output
The node outputs a binary file in the specified output field containing the video merged with the provided audio track. The json output typically includes metadata about the processed file, but the main result is the combined media file accessible via the named binary property.
If the input files are binary data, the output binary field will contain the resulting video file with the new audio track embedded.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- The node depends on an external ffmpeg processing backend (likely accessed via API).
- Proper URLs or binary inputs must be provided for both video and audio sources.
Troubleshooting
- Invalid Input URLs or Binary Fields: Ensure that the video and audio inputs are either valid URLs or correctly named binary fields containing media data.
- Unsupported Formats: The node may fail if the input video or audio formats are not supported by the ffmpeg backend.
- Missing API Credential: The node requires a valid API authentication token; missing or invalid credentials will cause errors.
- Output Field Conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow data.
Common error messages might indicate:
- Failure to fetch input files (check URLs and network access).
- Unsupported codec or format errors (convert inputs beforehand if needed).
- Authentication failures (verify API key configuration).