NCA Toolkit icon

NCA Toolkit

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

Actions15

Overview

The node provides video processing capabilities, specifically allowing users to trim videos by specifying start and end times. It supports inputting a video URL and optional encoding options such as audio bitrate, audio codec, video codec, video CRF, and video preset. Users can also specify a webhook URL to receive notifications when processing is complete and a custom job ID for tracking. This node is useful for scenarios where users need to extract specific segments from videos, such as creating highlights, previews, or removing unwanted sections.

Use Case Examples

  1. Trimming a video from 1 minute to 3 minutes to create a highlight clip.
  2. Extracting a segment from a longer video for social media sharing.
  3. Processing a video with custom encoding settings to optimize quality and file size.

Properties

Name Meaning
Video URL URL of the video file to process, required input.
Start Start time for trimming the video, formatted as hh:mm:ss or mm:ss.
End End time for trimming the video, formatted as hh:mm:ss or mm:ss.
Encoding Options Optional encoding settings for audio bitrate, audio codec, video codec, video CRF, and video preset to customize output quality and format.
Webhook URL Optional URL to receive a webhook notification when processing is complete.
Custom Job ID Optional custom identifier for tracking this request.

Output

JSON

  • id - Identifier of the processing job or request.
  • status - Current status of the video processing job.
  • result
    • url - URL of the processed trimmed video file.
  • message - Additional message or information about the processing result.

Dependencies

  • Requires an API key credential for the No Code Architects Toolkit API to authenticate requests.

Troubleshooting

  • Ensure the video URL is accessible and correctly formatted; invalid URLs will cause processing errors.
  • Start and end times must be in the correct format (hh:mm:ss or mm:ss) and the end time must be after the start time.
  • If encoding options are provided, ensure they are valid values supported by the API to avoid encoding failures.
  • Webhook URL must be reachable and correctly configured to receive notifications.
  • Timeout or network issues may occur if the server is slow or unreachable; adjust timeout settings or proxy configuration if needed.

Links

Discussion