Actions12
Overview
This node interacts with the Nexrender API to manage rendering jobs and perform health checks on the Nexrender service. Specifically, the "Health Check" operation verifies the availability and status of the Nexrender server by sending a GET request to its health endpoint. This is useful for monitoring whether the Nexrender service is up and responsive before submitting rendering jobs or performing other operations.
Practical examples:
- Before starting a batch of rendering jobs, use the Health Check operation to ensure the Nexrender server is online.
- Integrate this node in workflows that require conditional logic based on the Nexrender service status.
Properties
| Name | Meaning |
|---|---|
| Manual Assets JSON | JSON-formatted string representing assets for the job, used when overriding default assets. |
Note: For the Health Check operation specifically, no input properties are required or used.
Output
The node outputs an array with one item per input. Each output item contains a json field holding the response from the Nexrender API.
For the Health Check operation, the json output contains the health status information returned by the Nexrender server, typically including fields indicating server uptime, version, or readiness status.
No binary data is output by this node.
Dependencies
- Requires access to a Nexrender API endpoint.
- Requires an API authentication token credential to authorize requests to the Nexrender server.
- The node expects the Nexrender API domain and endpoint URL to be configured via credentials.
Troubleshooting
No credentials returned!
This error occurs if the node cannot retrieve the necessary API authentication token. Ensure that valid credentials are configured in n8n for the Nexrender API.API Response Error:
If the Nexrender server returns an error (e.g., 4xx or 5xx HTTP status), the node will throw an error containing the server's response message. Verify the API endpoint URL, token validity, and server availability.Unknown Error:
Indicates unexpected issues such as network problems or malformed requests. Check network connectivity and configuration.If the Health Check operation fails, confirm that the Nexrender server is running and accessible at the configured domain and endpoint.