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

Example: You have a video recording without sound and a separate audio commentary file. Using this node operation, you can combine them into one video file with the commentary embedded.

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 binary data representing the new video file with audio combined.

If the input was binary data, the output binary field will contain the resulting combined media file ready for further workflow steps or download.

Dependencies

  • Requires an API key credential for accessing the underlying ffmpeg service.
  • The node depends on an external ffmpeg processing backend accessible via the configured 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 files.
  • Missing or Incorrect API Credentials: The node requires a valid API authentication token to communicate with the ffmpeg service.
  • Unsupported Media Formats: The audio or video files must be in formats supported by ffmpeg; otherwise, processing may fail.
  • 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 invalid inputs, authentication failures, or processing errors from ffmpeg. Verify credentials, input correctness, and media compatibility to resolve these issues.

Links and References

Discussion