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 new rendering templates by sending a JSON payload describing the template details.
Common scenarios where this node is beneficial include:
- Automating the creation of video or animation templates for batch processing.
- Managing dynamic content rendering pipelines by programmatically updating or creating templates.
- Integrating Nexrender template management into larger automation workflows without manual API calls.
For example, you can create a new template with custom parameters such as type and display name, which can then be used in subsequent rendering jobs.
Properties
| Name | Meaning |
|---|---|
| Body | The JSON payload representing the template to create. This should conform to Nexrender's template schema. Example: {"type":"aep","displayName":"My Template"} |
Output
The node outputs the JSON response from the Nexrender API after creating the template. This typically includes details about the newly created template such as its ID, type, display name, and other metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Nexrender Cloud API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL for the API is taken from the credential configuration.
- The node uses HTTP methods (POST) to interact with the
/templatesendpoint of the Nexrender API.
Troubleshooting
- Invalid JSON in Body: If the "Body" property contains malformed JSON, the node will fail parsing it. Ensure the JSON is valid.
- Authentication Errors: Missing or incorrect API credentials will cause authorization failures. Verify that the API key/token is correctly set up.
- API Endpoint Errors: If the Nexrender service is unreachable or returns errors, check network connectivity and API status.
- Unexpected API Responses: If the API changes or returns unexpected data, the node may throw errors. Review the API documentation and update the payload accordingly.
- Error Messages: The node surfaces HTTP error codes and messages from the API, e.g., "HTTP 400: Bad Request" indicating invalid input.