Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
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 | The type of media being processed; options are "Video" or "Audio". |
| Filter and Effects (videoF) | For video media: a comma-separated list of filters and effects to apply (e.g., scale=640:480, grayscale). Required when Media File is Video. |
| Filter and Effects (audioF) | For audio media: a comma-separated list of filters and effects to apply. Required when 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 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 and effects.
If the media is video, the output binary contains the filtered video stream; if audio, it contains the filtered audio stream.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Depends on ffmpeg functionality exposed via an external API or service configured in n8n credentials.
- No additional environment variables are explicitly required beyond the API authentication setup.
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: Confirm that the media type matches the selected filters (video filters for video, audio filters for audio).
- API authentication issues: Verify that the API key credential is properly 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 data.
Common error messages may relate to:
- "Invalid filter graph" indicating filter syntax problems.
- "Input file not found" indicating incorrect input references.
- Authentication failures due to missing or invalid API keys.
Resolving these usually involves verifying inputs, correcting filter strings, and checking credential configurations.
Links and References
- FFmpeg Filters Documentation — Reference for filter syntax and available filters.
- n8n Documentation — General guidance on creating and configuring nodes and credentials.