Nexrender icon

Nexrender

Interact with Nexrender Cloud API

Actions14

Overview

This node interacts with the Nexrender Cloud API, specifically to manage rendering jobs and related resources. The "Job: Get" operation retrieves the status and details of a specific rendering job by its ID. It supports two modes:

  • Immediate retrieval: Fetch the current job status once.
  • Polling mode: Continuously check the job status at intervals until it finishes or errors out, useful for workflows that depend on the completion of rendering tasks.

Common scenarios include monitoring rendering jobs submitted to Nexrender Cloud, waiting for their completion before proceeding with further automation steps, or fetching job results for reporting or downstream processing.

Example use cases:

  • Automatically trigger video post-processing only after a Nexrender job finishes successfully.
  • Monitor long-running render jobs and handle errors promptly.
  • Retrieve job metadata or output information once rendering completes.

Properties

Name Meaning
ID The unique identifier of the Nexrender job to retrieve.
Wait Until Finished/Error Boolean flag indicating whether to poll the job status repeatedly until it finishes or errors.
Poll Interval (Seconds) Time interval in seconds between each status check when polling is enabled. Minimum 1 second.
Timeout (Minutes) Maximum time in minutes to wait for the job to finish before failing due to timeout. Minimum 1 minute.

Output

The node outputs a JSON object representing the full job details as returned by the Nexrender API. This includes fields such as job status, metadata, progress, and any result URLs or error messages.

If polling is enabled, the output will be the final job state after completion or error.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Nexrender Cloud API.
  • The base URL for the API is configurable via credentials.
  • Network access to the Nexrender Cloud API endpoint is necessary.

Troubleshooting

  • Timeout Errors: If the job does not finish within the specified timeout, the node throws a timeout error. Increase the timeout or verify the job's actual runtime.
  • Invalid Job ID: Providing a non-existent or malformed job ID will cause API errors. Verify the job ID correctness.
  • API Authentication Failures: Ensure the API key credential is valid and has appropriate permissions.
  • Polling Interval Too Low: Setting the poll interval below 1 second is not allowed and may cause errors.
  • No Binary Data Found: Not applicable for this operation but relevant for other operations involving file uploads.

Links and References

Discussion