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 recorded audio (e.g., voiceover) with video footage.
Example: You have a video file without sound and a separate audio recording. Using this node, you can input both files and output a new video file that contains the video visuals along with the provided audio track.
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+audio file will be stored. |
Output
The node outputs a binary file in the specified output field name containing the resulting video with the combined audio track. The json output typically includes metadata about the processed file, but the main content is the binary data representing the merged video and audio.
If the input was binary data, the output binary field will contain the newly created video file with the audio embedded.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Relies on an external ffmpeg processing backend accessible via the configured API.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Invalid Input URLs or Binary Fields: Ensure that the video and audio inputs are either valid URLs or correctly named binary fields present in the incoming data.
- Unsupported Formats: The node depends on ffmpeg capabilities; unsupported video or audio formats may cause errors.
- API Authentication Errors: Verify that the API key credential is correctly set up and has permissions to use the ffmpeg service.
- Output Field Conflicts: Make sure the output binary field name does not conflict with existing fields to avoid overwriting important data.
Common error messages might indicate missing inputs, invalid URLs, or failed processing due to format incompatibility. Checking the input data and credentials usually resolves these issues.