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 | Selects the type of media: "Video" or "Audio". |
| Filter and Effects | For Video: a comma-separated list of video filters/effects to apply (e.g., scale=640:480, grayscale).For Audio: a comma-separated list of 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 but primarily the binary data holds the filtered media content.
If the media is video, the output binary will be the transformed video file; if audio, the transformed audio file.
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: If the input media URL or binary field name is incorrect or inaccessible, the node will fail to process. Ensure the input points to a valid media source.
- Filter syntax errors: Incorrectly formatted filter strings (e.g., missing commas or invalid filter names) can cause ffmpeg to error out. Validate filter expressions before use.
- Unsupported media type: Selecting a media type that does not match the actual input file may lead to processing errors.
- API authentication issues: Missing or invalid API credentials will prevent the node from communicating with the ffmpeg service.
Common error messages might include:
- "Failed to load input media" — check input path or binary field.
- "Filter graph parsing failed" — verify filter syntax.
- "Authentication failed" — confirm API key validity.