NCA Toolkit icon

NCA Toolkit

Process media files using the No Code Architects Toolkit API

Overview

This node interacts with the No Code Architects Toolkit API to retrieve the status of all jobs processed within a specified recent time frame. It is useful for monitoring and tracking the progress or completion of media processing jobs, such as audio, video, or media operations. For example, a user can request the status of all jobs processed in the last 10 minutes and optionally receive a webhook notification when processing is complete.

Use Case Examples

  1. Retrieve all job statuses from the last 600 seconds (10 minutes) to monitor recent processing activity.
  2. Use a custom job ID to track a specific request for job statuses.
  3. Set a webhook URL to get notified when the job status retrieval process is complete.

Properties

Name Meaning
Since Seconds Number of seconds to look back for jobs. Defines the time window for retrieving job statuses, defaulting to 600 seconds (10 minutes).
Webhook URL Optional URL to receive a webhook notification when processing is complete.
Custom Job ID Optional custom identifier for tracking this request.
Request Options Additional request settings such as batching, SSL certificate validation, proxy configuration, and request timeout.

Output

JSON

  • jobs - Array of job status objects retrieved from the API, representing the status of each job within the specified time frame.

Dependencies

  • No Code Architects Toolkit API

Troubleshooting

  • If the API key or base URL credentials are incorrect or missing, the node will fail to authenticate and retrieve job statuses. Verify credentials in the node settings.
  • If the 'Since Seconds' value is set too low, the API may return no jobs because the time window is too narrow. Increase the value to widen the search period.
  • If the webhook URL is invalid or unreachable, webhook notifications will fail. Ensure the URL is correct and accessible from the API server.
  • SSL certificate validation errors can occur if the server uses a self-signed or invalid certificate. Enable 'Ignore SSL Issues' to bypass this, but be aware of security risks.
  • Proxy settings must be correctly configured if a proxy is required. Incorrect proxy details will cause request failures.

Links

Discussion