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). |
| Filter and Effects | 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 field typically contains metadata or status information about the operation, while the actual media data is stored in the binary output field.
If the media is video, the output binary contains the filtered video file; if audio, it contains the filtered 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 from the static code.
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 media type inconsistent with the input file may lead to errors.
- Missing API credentials: The node requires a valid API key credential to communicate with the ffmpeg service.
- Output field conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow.
Common error messages might relate to invalid filter parameters or inaccessible media inputs. Verifying filter strings and input availability usually resolves these issues.