Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node provides video processing capabilities using ffmpeg, specifically supporting a "Trim & Merge Video" operation under the "Video Processing" resource. It allows users to input a video URL and specify multiple highlight segments (time ranges with reasons) to trim from the original video and merge them into a single output video. Optionally, transitions can be added between these trimmed segments to create a smooth visual flow.
Common scenarios for this node include:
- Creating highlight reels by extracting key moments from long videos.
- Generating summarized versions of events or presentations.
- Editing raw footage by cutting out irrelevant parts and merging important clips seamlessly.
For example, a user might input a lecture video URL and specify highlights such as introduction, main topics, and conclusion with their respective time ranges. The node will then produce a merged video containing only those segments, optionally adding fade transitions between them.
Properties
| Name | Meaning |
|---|---|
| Video Url | A valid URL pointing to the source video to be processed. |
| Video Highlights | JSON string representing an array of objects, each specifying a highlight segment with highlight_reason (description) and highlight_time (time range in format "HH:MM - HH:MM"). Example: [{"highlight_reason": "Introduction", "highlight_time": "00:00 - 00:10"}, {"highlight_reason": "Main event", "highlight_time": "01:00 - 01:30"}]. |
| Add Transitions | Boolean flag indicating whether to add transitions between the trimmed video segments. |
| Transition Type | If transitions are enabled, specifies the type of transition effect to apply between segments. Options are: "Fade White" or "Fade Black". |
Output
The node outputs a JSON object representing the processed video result. This typically includes metadata about the newly created video file after trimming and merging the specified segments. If binary data output is supported (not explicitly shown in the provided code), it would represent the final video file content.
In summary, the json output field contains details about the processed video, such as its location or metadata. Binary output (if any) would contain the actual video file data ready for further use or download.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service or API.
- Relies on external ffmpeg functionality exposed via an API endpoint configured in n8n credentials.
- The node expects internet access to fetch the video from the provided URL.
- No other explicit environment variables or configurations are indicated in the static code.
Troubleshooting
- Invalid Video URL: Ensure the provided video URL is accessible and points to a valid video file. Network issues or incorrect URLs will cause failures.
- Malformed Highlights JSON: The
Video Highlightsproperty must be a correctly formatted JSON string representing an array of objects withhighlight_reasonandhighlight_time. Invalid JSON or missing fields will cause errors. - Transition Errors: If transitions are enabled but an unsupported transition type is selected or the ffmpeg service does not support it, the node may fail.
- API Credential Issues: Missing or invalid API authentication tokens will prevent the node from executing successfully.
- Time Range Format: Highlight times must follow the "HH:MM - HH:MM" format exactly; otherwise, parsing errors may occur.
Links and References
- FFmpeg Official Documentation – For understanding video processing concepts and supported filters/effects.
- JSON Syntax Guide – To help format the
Video Highlightsproperty correctly. - n8n Documentation – For general guidance on setting up credentials and using custom nodes.