ffmpeg Node icon

ffmpeg Node

n8n Node for some Ffmpeg functionality
Join our community

Actions11

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 combined audio and video streams.

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. Default is "data".

Output

The node outputs a binary file in the specified output field (default "data") which contains the resulting video with the combined audio track. The json output typically includes metadata about the processed file, such as filename, mime type, or other relevant information.

If the input files are provided as binary data, the output will also be binary data representing the merged video file.

Dependencies

  • Requires an API key credential for accessing the underlying ffmpeg service.
  • The node depends on an external ffmpeg processing backend accessible via API.
  • Proper configuration of the API credentials in n8n is necessary for the node to function.

Troubleshooting

  • Invalid input URLs or binary fields: Ensure that the video and audio inputs are correctly specified either as valid URLs or existing binary fields in the workflow.
  • Unsupported file formats: The node relies on ffmpeg capabilities; unsupported or corrupted media files may cause errors.
  • API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Output field conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow to avoid overwriting data unintentionally.

Common error messages might indicate missing inputs, invalid media formats, or authentication failures. Checking the input parameters and credential setup usually resolves these issues.

Links and References

Discussion