Actions14
Overview
This node interacts with the Nexrender Cloud API, specifically to manage templates among other resources. The "Get Upload URL" operation for the Template resource generates a pre-signed URL that allows uploading content directly to the template's storage location. This is useful when you want to programmatically upload assets or files associated with a specific template in Nexrender without handling the file transfer yourself.
Practical scenarios include:
- Automating the upload of video or image assets to a Nexrender template before rendering.
- Integrating Nexrender template management into larger workflows where templates and their assets are dynamically updated.
- Enabling secure, time-limited upload access to template storage locations.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the template for which to get the upload URL. |
Output
The output JSON contains the response from the Nexrender API for the upload URL request. Typically, this includes a URL string or an object containing the signed upload URL and possibly additional metadata required to perform the upload.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"uploadUrl": "https://signed-upload-url.example.com/..."
}
Dependencies
- Requires an API key credential for authenticating with the Nexrender Cloud API.
- The node expects the base URL of the Nexrender API to be configured via credentials.
- Network access to the Nexrender API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing template ID will cause the API call to fail.
- Authentication errors if the API key credential is incorrect or expired.
- Network connectivity problems preventing access to the Nexrender API.
Error messages:
- HTTP errors with status codes and messages returned from the Nexrender API, e.g.,
HTTP 404: Template not found. - Timeout errors if the API does not respond in time.
- Parsing errors if the response is malformed.
- HTTP errors with status codes and messages returned from the Nexrender API, e.g.,
Resolutions:
- Verify the template ID is correct and exists in your Nexrender account.
- Ensure the API key credential is valid and has appropriate permissions.
- Check network connectivity and firewall settings.
- Enable "Continue on Fail" in the node settings to handle errors gracefully in workflows.