Nexrender icon

Nexrender

Interact with Nexrender Cloud API
Join our community

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 defined intervals until it finishes or errors out, or until a timeout is reached.

This functionality is useful in workflows where you need to monitor the progress of video rendering or automation tasks managed by Nexrender, enabling conditional logic or further processing based on job completion.

Practical examples:

  • Trigger downstream actions only after a video rendering job completes successfully.
  • Monitor a long-running render job and update a dashboard or notify users upon completion or failure.
  • Implement retry or error handling logic if the job fails.

Properties

Name Meaning
ID The unique identifier of the Nexrender job to retrieve.
Wait Until Finished/Error Whether to keep polling the job status until it reaches a finished or error state (true/false).
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 throwing a timeout error. Minimum 1 minute.

Output

The node outputs a JSON object representing the job's current state as returned by the Nexrender API. This includes all job details such as status, metadata, and any relevant result information.

If polling is enabled, the output will be the final job state once it has finished or errored, or an error if the timeout is reached.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Nexrender Cloud API.
  • The base URL for the API is configurable via credentials.
  • Uses HTTP requests with JSON payloads and expects JSON responses.
  • No additional external dependencies beyond standard HTTP and authentication helpers provided by n8n.

Troubleshooting

  • Common issues:

    • Invalid or missing Job ID will cause the API request to fail.
    • Network or authentication errors can prevent successful API calls.
    • If polling is enabled, the node may timeout if the job takes longer than the configured timeout period.
    • Missing or incorrect API credentials will cause authorization failures.

  • Error messages:

    • "Timed out waiting for job <ID> after <timeout> minutes": Indicates the job did not reach a terminal state within the allowed time. Increase timeout or verify job status externally.
    • HTTP errors with status codes and messages from the Nexrender API are propagated. Check API key validity and network connectivity.
    • "No binary data found under property '<propertyName>'": Not applicable for this operation but may appear if other operations requiring binary input are used incorrectly.

  • Resolution tips:

    • Verify the Job ID exists and is correct.
    • Ensure the API key credential is valid and has necessary permissions.
    • Adjust polling interval and timeout settings according to expected job duration.
    • Check network access to the Nexrender API endpoint.

Links and References

Discussion