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 - List" operation retrieves a list of rendering jobs from the Nexrender service. This is useful for workflows that need to monitor, audit, or process multiple rendering jobs, such as fetching all current or past jobs with optional filtering.

Practical examples include:

  • Automatically retrieving all rendering jobs created within a certain timeframe.
  • Filtering jobs by status or other metadata to trigger further processing.
  • Integrating Nexrender job data into dashboards or reporting tools.

Properties

Name Meaning
Query Parameters Key-value pairs used as query parameters to filter the list of jobs returned by the API.

The "Query Parameters" property allows specifying multiple key-value pairs that are sent as URL query parameters to filter the jobs list. For example, you could filter jobs by status, creation date, or any other supported query parameter defined by the Nexrender API.

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 with details such as job ID, status, creation time, and other metadata.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "jobs": [
    {
      "id": "job-id-123",
      "status": "finished",
      "createdAt": "2024-01-01T12:00: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.
  • The node uses HTTP GET requests to fetch job data.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect query parameters may result in empty results or API errors.
    • Network connectivity issues can prevent communication with the Nexrender API.

  • Error messages:

    • Errors from the API are parsed and presented with HTTP status codes and error messages.
    • Timeout or network errors will be surfaced as request failures.

  • Resolutions:

    • Verify that the API key credential is correctly configured and has necessary permissions.
    • Check the format and validity of query parameters.
    • Ensure stable internet connection and correct API base URL.

Links and References

Discussion