ffmpeg Node icon

ffmpeg Node

n8n Node for some Ffmpeg functionality

Actions11

Filters and Effect → Add Filters

AI-generated

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 to resize and desaturate the video, and receive the processed video as output. Similarly, for audio, filters could be applied to adjust volume, equalize sound, or add effects.

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 that will contain the processed media file.
Media File The type of media being processed; options are "Video" or "Audio".
Filter and Effects (video) A comma-separated list of ffmpeg video filters and effects to apply (e.g., scale=640:480,grayscale). Required if Media File is Video.
Filter and Effects (audio) A comma-separated list of ffmpeg audio filters and effects to apply. Required if Media File is Audio.

Output

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

If the input was a video, the output binary will be the filtered video stream; if audio, the filtered audio stream. This allows subsequent nodes in the workflow to use or store 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 credential.
  • No additional environment variables are explicitly required beyond the API authentication.

Troubleshooting

  • Invalid media input: Ensure the input field contains a valid media URL or binary data. Invalid or missing inputs will cause processing errors.
  • Incorrect filter syntax: Filters must be specified correctly according to ffmpeg filter syntax. Malformed filters can cause the node to fail.
  • Mismatched media type and filters: Applying video filters to audio media or vice versa will likely result in errors.
  • API authentication issues: Verify that the API key credential is correctly configured and has necessary permissions.
  • Output field conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow data.

Common error messages will relate to invalid input, filter parsing failures, or authentication problems. Reviewing the filter strings and verifying credentials usually resolves these issues.

Links and References

Discussion