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 visual effects like resizing or color adjustments to videos.
  • Applying audio filters such as volume normalization or equalization.
  • 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 that will contain the processed media file.
Media File Selects the type of media: 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 output contains the media after applying the requested filters and effects.

  • The json output field typically includes metadata about the operation or the processed media.
  • The binary output field contains the transformed media file (video or audio), ready for further use or export.

Dependencies

  • Requires an API key credential for accessing the underlying ffmpeg service.
  • The node depends on ffmpeg functionality exposed via an external API or service configured in n8n.
  • Proper configuration of this API credential is necessary for the node to function.

Troubleshooting

  • Common issues:

    • Invalid media input URL or missing binary data in the specified input field.
    • Incorrect filter syntax or unsupported filter names can cause processing failures.
    • Mismatch between selected media type and provided filters (e.g., applying video filters to audio).

  • Error messages:

    • Errors related to media loading usually indicate invalid input references or inaccessible URLs.
    • Filter parsing errors suggest syntax mistakes; verify filter strings against ffmpeg documentation.
    • Authentication errors point to misconfigured or missing API credentials.

  • Resolutions:

    • Ensure the input media field or URL is correct and accessible.
    • Validate filter expressions independently with ffmpeg tools.
    • Confirm API credentials are correctly set up in n8n.

Links and References

Discussion