ClipMagic icon

ClipMagic

Interact with ClipMagic API for video and audio processing

Overview

The node integrates with the ClipMagic API to perform various video and audio processing tasks. Specifically, the "Compress Video" operation reduces the file size of a given video by applying compression settings such as encoding speed preset and quality factor. This is useful for optimizing videos for web delivery, saving storage space, or preparing files for faster streaming.

Practical examples:

  • Compressing large raw video footage to a smaller size before uploading to a content platform.
  • Reducing bandwidth usage by compressing marketing videos while maintaining acceptable quality.
  • Preparing videos for mobile devices where lower bitrate and faster encoding are beneficial.

Properties

Name Meaning
Video URL URL of the input video to be compressed.
Preset Encoding speed preset; options include Ultra Fast, Super Fast, Very Fast, Faster, Fast, Medium (default), Slow, Slower, Very Slow, Placebo. Faster presets encode quicker but with less compression efficiency.
CRF (Quality) Constant Rate Factor controlling quality: 18 = nearly lossless, 23 = default, 28 = low quality. Lower values mean better quality but larger files.
Output Format Output container format; options are MP4, MOV, AVI.
Options Extra settings for the request. Currently supports: Timeout (ms) - how long to wait before aborting the HTTP call (0 means no limit).

Output

The node outputs JSON data indicating success status, operation performed, output filename, and content type. If the response contains binary media data (video/audio), it is provided in the binary.data field prepared for further use in n8n workflows.

Output structure example (JSON part):

{
  "success": true,
  "operation": "compress",
  "filename": "output.mp4",
  "contentType": "video/mp4"
}

If binary data is returned, it will be accessible under the binary.data property, containing the compressed video file.

Dependencies

  • Requires an API key credential for authenticating with the ClipMagic API.
  • The node makes HTTP requests to the ClipMagic service base URL configured in the credentials.
  • No additional environment variables are required beyond the API authentication setup.

Troubleshooting

  • Timeouts: If the compression takes longer than the specified timeout, the request will abort. Increase the timeout value in the "Options" if needed.
  • Invalid URLs: Ensure the "Video URL" points to a valid, accessible video file. Invalid or inaccessible URLs will cause errors.
  • Unsupported formats: The input video must be supported by the ClipMagic API. Unsupported formats may result in failure.
  • API errors: Errors from the ClipMagic API will be returned in the node output. Check the error message for details.
  • Credential issues: Make sure the API key credential is correctly configured and has necessary permissions.

Links and References

Discussion