Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node provides video processing capabilities focused on trimming and merging video segments based on user-defined highlights. It allows users to specify multiple highlight time ranges within a video URL, extract those segments, and merge them into a single output video. Optionally, transitions can be added between the merged segments to create smooth visual effects.
Common scenarios where this node is beneficial include:
- Creating highlight reels from longer videos by extracting key moments.
- Editing event footage to keep only important parts.
- Generating summarized versions of tutorials or presentations.
- Adding professional transitions between clips for polished video outputs.
For example, a user could input a full-length webinar video URL along with JSON specifying start and end times of key topics discussed. The node would then trim those segments and merge them, optionally adding fade transitions between each segment.
Properties
| Name | Meaning |
|---|---|
| Video Url | A valid URL pointing to the source video to be processed. |
| Video Highlights | JSON array of objects specifying highlight segments to trim. Each object contains highlight_reason (description) and highlight_time (time range in "HH:MM - HH:MM" format). 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 trimmed video segments. |
| Transition Type | Type of transition effect to apply between segments if transitions are enabled. Options: Cross Zoom, Dissolve, Fade, Wipe Left, Wipe Right. |
| Transition Duration | Duration in seconds for the transition effect between video segments. |
Output
The node outputs a JSON object containing the processed video data. This typically includes the merged video file after trimming the specified highlights and applying optional transitions. If binary data output is supported, it will contain the final video file in a binary field suitable for further workflow steps such as uploading or saving.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg-based video processing service.
- The node depends on external video processing capabilities exposed via an API (likely ffmpeg functionality wrapped in a service).
- Proper network access to the provided video URLs is necessary.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Invalid Video URL: Ensure the video URL is accessible and points to a valid video file format supported by the service.
- Malformed Highlights JSON: The
Video Highlightsproperty must be a correctly formatted JSON string representing an array of objects withhighlight_reasonandhighlight_time. Invalid JSON or incorrect time formats may cause errors. - Transition Errors: If transitions are enabled but the type or duration is invalid, the node might fail. Use one of the predefined transition types and provide a positive number for duration.
- API Authentication Failures: Verify that the API key credential is correctly configured and has permissions for video processing.
- Timeouts or Large Videos: Processing very large videos or many segments may lead to timeouts or performance issues depending on the backend service limits.
Links and References
- FFmpeg Official Documentation – For understanding video processing concepts and supported formats.
- JSON Format Guide – To ensure correct formatting of the highlights input.
- n8n Documentation – For general guidance on using credentials and configuring nodes.