NCA Toolkit icon

NCA Toolkit

Process media files using the No Code Architects Toolkit API
Join our community

Actions15

Overview

This node, part of the NCA Toolkit, processes media files by converting them from one format to another using the No Code Architects Toolkit API. It is useful for scenarios where users need to transform media files (e.g., videos) into different formats such as mp4, webm, or avi, with customizable audio and video encoding options. For example, a user can convert a video from an online URL to an mp4 format with specific audio bitrate and video codec settings.

Use Case Examples

  1. Converting a video from a URL to mp4 format with default encoding settings.
  2. Converting a media file to webm format with custom audio bitrate and video codec.
  3. Using a webhook URL to get notified when the media conversion is complete.

Properties

Name Meaning
Media URL URL of the media file to process, required input for conversion.
Output Format Desired output format for the media file, e.g., mp4, webm, avi.
Conversion Options Optional settings for audio bitrate, audio codec, video codec, video CRF (quality), and video preset to customize the conversion process.
Webhook URL Optional URL to receive a webhook notification when processing is complete.
Custom Job ID Optional custom identifier for tracking the conversion request.
Request Options Settings for batching requests, SSL certificate validation, proxy usage, and request timeout.

Output

JSON

  • convertedMediaUrl - URL of the converted media file returned by the API.
  • jobId - Identifier for the conversion job, useful for tracking.
  • status - Status of the conversion process (e.g., pending, completed).
  • webhookNotification - Information about webhook notification if webhook URL was provided.

Dependencies

  • No Code Architects Toolkit API
  • API key credential for authentication

Troubleshooting

  • Ensure the Media URL is accessible and correctly formatted; invalid URLs will cause request failures.
  • Verify the output format is supported by the API; unsupported formats will result in errors.
  • If using a webhook URL, ensure it is publicly accessible to receive notifications.
  • Check API key validity and permissions if authentication errors occur.
  • If SSL issues arise, consider enabling the option to ignore SSL certificate validation, but be aware of security risks.

Links

Discussion