Actions7
Overview
The ClipMagic node integrates with the ClipMagic API to perform various video and audio processing tasks. For the "Convert Media" operation, it converts media files from one format to another, supporting both audio and video formats. This is useful when you need to change file types for compatibility, reduce file size, or prepare media for specific platforms.
Practical examples include:
- Converting a WAV audio file to MP3 for easier streaming.
- Changing a video from MOV to MP4 format for better device support.
- Scaling a video resolution down to 720p to reduce bandwidth usage.
Properties
| Name | Meaning |
|---|---|
| Media URL | Direct URL to the media file or a Google Drive share link to be converted. |
| Output Format | Target container format for the output media. Options: MP3, WAV, AAC, MP4, MOV |
| Resolution | Video height scaling option (ignored for audio). Options: Original, 360p, 480p, 720p, 1080p |
| Bitrate (kbps) | Target video bitrate in kbps (max 3000). Set to 0 for automatic bitrate selection. |
| Options | Extra settings collection: |
| - Timeout (ms) | How long to wait before aborting the HTTP call. Set to 0 for no limit. Default is 600000 ms. |
Output
The node outputs JSON data indicating success and details about the operation performed. If the response contains media content (audio/video), it outputs binary data under the binary.data field along with metadata:
json.success: Boolean indicating if the operation succeeded.json.operation: The operation name ("convert").json.filename: The filename of the returned media (extracted from response headers or defaulted).json.contentType: MIME type of the returned media.binary.data: The actual converted media file in binary form.
If the response is JSON (e.g., status or metadata), it outputs that JSON directly under json.
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 credentials.
- No additional environment variables are required beyond the API authentication setup.
Troubleshooting
- Timeouts: If conversions take too long, increase the timeout value in options or set it to 0 for unlimited.
- Invalid URLs: Ensure the media URL is accessible and direct (Google Drive links must be shareable).
- Unsupported formats: Check that the input media format is supported by ClipMagic and that the output format is valid.
- API errors: Errors from the API will be returned as JSON with error messages; verify your API key and request parameters.
- Binary data issues: If the output binary data is missing or corrupted, confirm the content-type header indicates media and that the file was properly downloaded.
Links and References
- ClipMagic Official Website
- ClipMagic API Documentation (hypothetical link for reference)