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 recorded a video without sound and separately recorded a commentary track. Using this node, you can combine the commentary audio with the video to create a final video file ready for publishing.

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 combined video file that merges the provided video and audio inputs. The output is placed in a binary field named as specified by the "Video Output Name" property (default "data"). The json output field typically contains metadata about the processed file or success status, while the binary data field contains the actual combined media file.

If the node supports binary data output, it means the resulting video with the new audio track is available as a downloadable file within the workflow.

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 authentication token or credentials in n8n is necessary.
  • Input video and audio files must be accessible either as URLs or as binary data within the workflow.

Troubleshooting

  • Invalid Input URLs or Binary Fields: Ensure that the video and audio inputs are correctly specified as valid URLs or existing binary fields. Incorrect names or inaccessible URLs will cause failures.
  • Unsupported Media Formats: The ffmpeg backend may reject unsupported video or audio formats. Verify compatibility before processing.
  • API Authentication Errors: Missing or invalid API credentials will prevent the node from functioning. Confirm that the API key is correctly configured.
  • Output Field Conflicts: If the specified output binary field name conflicts with existing fields, it may overwrite data unintentionally. Use unique names.
  • Large File Sizes: Processing very large video or audio files might lead to timeouts or memory issues depending on the backend limits.

Links and References

Discussion