Nexrender

Interact with Nexrender Cloud API

Actions14

Template Actions
Job Actions
Font Actions
Secret Actions
- Create
- Delete

Overview

This node interacts with the Nexrender Cloud API to manage video rendering templates and related resources. Specifically, the "Get Download URL" operation for the "Template" resource retrieves a URL that can be used to download the upload associated with a given template. This is useful when you want to programmatically access or download the assets uploaded to a specific template in Nexrender.

Common scenarios include:

Automating retrieval of template upload URLs for further processing or integration.
Managing video rendering workflows by accessing template assets dynamically.
Integrating Nexrender template management into larger automation pipelines.

Example: You have created a template in Nexrender and want to get the direct URL to the uploaded files so you can download or verify them as part of your workflow.

Properties

Name	Meaning
ID	Template ID (string) - The unique identifier of the template for which to get the download URL.

Output

The output JSON contains the response from the Nexrender API endpoint /templates/{templateId}/upload accessed via HTTP GET. This typically includes the download URL or related metadata about the upload associated with the specified template.

The exact structure depends on the Nexrender API but generally will contain fields such as:

A URL string to download the upload.
Possibly additional metadata about the upload.

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 (defaulting to https://api.nexrender.com/api/v2).
Network connectivity to the Nexrender Cloud API endpoint.

Troubleshooting

Missing or invalid Template ID: Ensure the "ID" property is provided and correctly references an existing template.
Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
Network issues: Check connectivity to the Nexrender API endpoint.
API errors: The node surfaces HTTP error messages; common ones include 404 if the template does not exist, or 401/403 for authentication/authorization failures.
If the node throws an error like Request failed with HTTP status code, check the message for details and ensure parameters and credentials are correct.