ffmpeg Node icon

ffmpeg Node

n8n Node for some Ffmpeg functionality

Actions11

Overview

This node integrates ffmpeg functionality into n8n workflows, focusing here on adding filters and effects to media files. It supports both video and audio media types, allowing users to apply custom filter chains to transform the input media. Typical use cases include resizing videos, applying grayscale or other visual effects to video streams, or modifying audio streams with various audio filters.

For example, a user might input a video file URL or binary data, specify filters like scale=640:480,grayscale for video, and receive the processed video as output. Similarly, audio files can be processed with audio-specific filters.

Properties

Name Meaning
Media File Input A valid media URL or the name of the input binary field containing the media file.
Media File Output The name of the output binary field where the processed media file will be stored.
Media File The type of media being processed; options are "Video" or "Audio".
Filter and Effects (videoF) For video media only: a comma-separated string of ffmpeg video filters/effects to apply.
Filter and Effects (audioF) For audio media only: a comma-separated string of ffmpeg audio filters/effects to apply.

Output

The node outputs the processed media file in a binary field named as specified by the "Media File Output" property. The json output contains metadata about the operation or the processed media but primarily the binary data holds the transformed media content.

If the input was a video, the output binary will contain the filtered video stream; if audio, the filtered audio stream. This allows downstream nodes to further process or save the modified media.

Dependencies

  • Requires an API key credential for accessing the underlying ffmpeg service.
  • The node depends on an external ffmpeg processing backend accessible via this API.
  • No additional environment variables are explicitly required beyond the API authentication.

Troubleshooting

  • Invalid media input: Ensure the input is a valid URL or a correctly named binary field containing media data.
  • Filter syntax errors: Filters must be valid ffmpeg filter strings separated by commas. Incorrect syntax will cause processing failures.
  • Unsupported media type: Selecting a media type that does not match the input file may cause errors.
  • API authentication issues: Verify that the API key credential is correctly configured and has necessary permissions.
  • Output binary field conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow.

Common error messages likely relate to invalid filter expressions or failed media processing due to unsupported formats or corrupted inputs.

Links and References

Discussion