NCA Toolkit icon

NCA Toolkit

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

Actions15

Overview

This node interacts with the No Code Architects Toolkit API to retrieve the status of an asynchronous job using a provided Job ID. It is useful for workflows that involve processing media files or other operations where tasks are handled asynchronously, allowing users to check the progress or completion status of these tasks. For example, after submitting a media file for processing, this node can be used to poll the job status until the processing is complete.

Use Case Examples

  1. Checking the status of a video processing job by providing the Job ID returned from the initial request.
  2. Using the webhook URL property to receive a notification when the job processing is complete, enabling event-driven workflow continuation.

Properties

Name Meaning
Job ID The unique identifier of the asynchronous job whose status is being queried. This is required to fetch the job status.
Webhook URL An optional URL to receive a webhook notification when the job processing is complete. If provided, the API will send a notification to this URL.
Custom Job ID An optional custom identifier for tracking the request, useful for correlating requests and responses in complex workflows.
Request Options Settings to control request behavior such as batching, SSL certificate validation, proxy usage, and timeout duration.

Output

JSON

  • job_id - The unique identifier of the job whose status was requested.
  • status - The current status of the job (e.g., pending, processing, completed, failed).
  • result - Details or output of the job if available, such as processed media information or error messages.

Dependencies

  • Requires an API key credential for authenticating with the No Code Architects Toolkit API.

Troubleshooting

  • Ensure the Job ID provided is correct and corresponds to an existing asynchronous job; otherwise, the API may return an error or no data.
  • If using a webhook URL, verify that the URL is accessible and correctly configured to receive POST requests from the API.
  • Timeout errors may occur if the server is slow to respond; consider increasing the timeout setting in request options.
  • If SSL certificate validation fails and you trust the endpoint, enable the option to ignore SSL issues, but be aware of the security implications.

Discussion