Actions14
Overview
This node integrates with the Nexrender Cloud API, enabling users to manage rendering templates and jobs programmatically within n8n workflows. Specifically, for the Template - Create operation, it allows creating a new template by sending a JSON payload describing the template details to the Nexrender service.
Common scenarios where this node is beneficial include automating video or animation rendering pipelines, dynamically generating templates based on input data, or managing templates in bulk without manual intervention.
For example, you can use this node to create a new rendering template that defines how an animation should be composed, which can then be used later to start rendering jobs automatically.
Properties
| Name | Meaning |
|---|---|
| Body | The JSON payload representing the template to create. This includes all necessary template details such as type, display name, assets, and other configuration parameters required by Nexrender. Example default value: {"type":"aep","displayName":"My Template"} |
Output
The node outputs a JSON object representing the response from the Nexrender API after creating the template. This typically includes details of the newly created template such as its unique identifier, metadata, and any other information returned by the API.
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). - The node uses HTTP requests with JSON payloads and expects JSON responses.
Troubleshooting
- Invalid JSON in Body property: If the "Body" input contains malformed JSON, the node will throw a parsing error. Ensure the JSON is valid before running the workflow.
- Authentication errors: If the API key credential is missing or invalid, the node will fail with an authentication error. Verify that the correct API key is configured.
- API endpoint errors: Errors returned by the Nexrender API (e.g., validation errors on the template payload) will be surfaced as node errors. Review the error message for details and adjust the payload accordingly.
- Network issues: Connectivity problems to the Nexrender API endpoint will cause request failures. Check network access and proxy settings if applicable.