ffmpeg Node icon

ffmpeg Node

n8n Node for some Ffmpeg functionality
Join our community

Actions11

Overview

This node provides functionality to add filters and effects to media files (video or audio) using ffmpeg capabilities. It is useful in scenarios where you want to programmatically apply transformations such as scaling, grayscale, or other filter chains to media content within an n8n workflow.

Practical examples include:

  • Adding a grayscale effect and resizing a video before uploading it.
  • Applying audio filters like volume adjustment or equalization to audio files.
  • Automating media processing pipelines that require consistent filter application.

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 Specifies the type of media: either "Video" or "Audio".
Filter and Effects (videoF) For video media only: a comma-separated list of filters and effects to apply (e.g., scale=640:480, grayscale).
Filter and Effects (audioF) For audio media only: a comma-separated list of filters and 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 field typically contains metadata about the operation or the processed file, but the main output is the transformed media binary data with the applied filters/effects.

If the media is video, the output binary contains the filtered video; if audio, the filtered audio.

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 media URL or binary field name is correct and accessible.
  • Filter syntax errors: Filters must be correctly formatted according to ffmpeg filter syntax; invalid filters will cause processing failures.
  • Unsupported media type: Selecting a filter for video when the media is audio (or vice versa) may cause errors.
  • API authentication issues: Verify that the API key credential is valid 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 might indicate:

  • "Failed to process media": Check media input and filter syntax.
  • "Authentication failed": Recheck API credentials.
  • "Unsupported filter": Validate filter strings against ffmpeg documentation.

Links and References

Discussion