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 | Select whether the media is "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). |
| Filter and Effects (audioF) | For audio media: 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
jsonoutput field typically includes metadata about the operation or the media but primarily the binary data field holds the transformed media. - Binary data represents the filtered video or audio file ready for further use or export.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Depends on an external ffmpeg processing backend accessible via the configured API.
- 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 selected media type matches the actual input (video vs audio).
- API authentication issues: Verify that the API key credential is valid and has necessary permissions.
- Output 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 load media": Check input source validity.
- "Filter parsing error": Review filter string syntax.
- "Authentication failed": Recheck API credentials.
Links and References
- FFmpeg Filters Documentation
- FFmpeg Official Website
- n8n documentation on working with binary data