ffmpeg Node icon

ffmpeg Node

n8n Node for some Ffmpeg functionality

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 sourced audio (e.g., voiceover) with video footage.

Practical 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 that contains both the visuals and the new 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 file (video + audio) will be stored.

Output

The node outputs a binary file in the specified output field containing the resulting video with the combined audio track. The json output typically includes metadata about the processed file, such as filename, mime type, and possibly duration or codec information depending on implementation details.

If the node supports binary data, the output binary field will contain the actual media file ready for further use or download.

Dependencies

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

Troubleshooting

  • Invalid input URLs or missing binary fields: Ensure that the video and audio inputs are correctly specified either as valid URLs or existing binary fields in the workflow.
  • API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • Unsupported media formats: The node relies on ffmpeg capabilities; unsupported or corrupted media files may cause failures.
  • 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 issues like "Failed to fetch input media," "Authentication failed," or "Unsupported format." Resolving these usually involves checking input correctness, credential validity, and media compatibility.

Links and References

Discussion