Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node provides video processing capabilities using ffmpeg functionality within n8n. Specifically, the "Trim Video" operation allows users to trim a video by specifying a time range. This is useful for extracting highlights or segments from longer videos without needing external video editing software.
Common scenarios include:
- Creating short clips from recorded webinars or tutorials.
- Extracting key moments from sports footage.
- Preparing video previews or teasers by trimming original content.
For example, a user can input a video URL and specify a trim time like "00:00 - 00:10" to get the first 10 seconds of the video as output.
Properties
| Name | Meaning |
|---|---|
| Video Url | A valid URL pointing to the source video to be trimmed. |
| Trim Time | The time range to trim the video, e.g., "00:00 - 00:10". Specifies the start and end times for the segment to extract. |
Output
The node outputs JSON data representing the result of the video trimming operation. Typically, this will include metadata about the trimmed video segment and possibly a reference (such as a URL or binary data field) to the trimmed video file itself.
If the node supports binary data output, it would contain the trimmed video file in a binary format accessible via a named binary property.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Depends on the ffmpeg backend service configured in n8n credentials.
- The node expects the input video to be accessible via the provided URL.
Troubleshooting
- Invalid Video URL: If the video URL is incorrect or inaccessible, the node will fail to fetch the video. Ensure the URL is publicly accessible or properly authenticated.
- Incorrect Trim Time Format: The trim time must follow a valid time range format (e.g., "HH:MM:SS - HH:MM:SS"). Invalid formats may cause errors or unexpected results.
- API Authentication Errors: Missing or invalid API credentials will prevent the node from executing. Verify that the API key credential is correctly set up.
- Unsupported Video Formats: The underlying ffmpeg service might not support certain video codecs or formats, leading to processing failures.