NexrenderInstall

Overview

This node interacts with the Nexrender Cloud API, specifically to manage rendering jobs and related resources. The "Job - List" operation retrieves a list of rendering jobs from the Nexrender service, optionally filtered by query parameters.

Typical use cases include:

• Fetching all rendering jobs to monitor their status or results.
• Filtering jobs based on specific criteria such as status, user, or other metadata.
• Integrating Nexrender job management into automated workflows for video rendering pipelines.

For example, you might use this node to get all jobs currently in progress or to retrieve jobs created by a particular user.

Properties

The "Query Parameters" property allows users to add any number of query filters that will be sent as URL query parameters to the Nexrender API's /jobs endpoint.

Example of query parameters usage:

[
  { "key": "status", "value": "finished" },
  { "key": "user", "value": "john_doe" }
]

This would request only jobs with status "finished" and created by user "john_doe".

Output

The output is a JSON object representing the response from the Nexrender API's /jobs endpoint. It typically contains an array of job objects, each describing a rendering job with details such as job ID, status, creation time, and other metadata provided by Nexrender.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "jobs": [
    {
      "id": "job_123",
      "status": "finished",
      "createdAt": "2024-01-01T12:00:00Z",
      "metadata": { ... }
    },
    {
      "id": "job_124",
      "status": "error",
      "createdAt": "2024-01-02T15:30:00Z",
      "metadata": { ... }
    }
  ]
}

Dependencies

• Requires an API key credential for authenticating with the Nexrender Cloud API.
• The base URL for the API is configurable via credentials (defaulting to https://api.nexrender.com/api/v2).
• The node uses HTTP GET requests to fetch job data.
• No additional external dependencies beyond the Nexrender API and n8n's HTTP request capabilities.

Troubleshooting

• Common issues:

  • Invalid or missing API authentication token will cause authorization errors.
  • Incorrect query parameter keys or values may result in empty responses or API errors.
  • Network connectivity problems can cause request failures.

• Error messages:

  • Errors are wrapped and presented with HTTP status codes and messages from the Nexrender API.
  • Timeout or network errors will indicate failure to reach the API endpoint.
  • If the node throws an error like Operation not implemented, it means the requested resource-operation combination is unsupported.

• Resolutions:

  • Ensure the API key credential is correctly configured and has necessary permissions.
  • Verify query parameters conform to Nexrender API documentation.
  • Check network access and proxy settings if applicable.

Links and References

• Nexrender Cloud API Documentation
• Nexrender GitHub Repository
• n8n Documentation on HTTP Request Node (for understanding underlying request mechanics)