Actions12
Overview
This node integrates with the Nexrender API to manage rendering jobs for After Effects automation. It supports various operations such as creating, updating, retrieving, listing, deleting jobs, and performing a health check on the Nexrender service.
The Health Check operation specifically sends a request to verify the availability and status of the Nexrender server. This is useful for monitoring and ensuring that the rendering backend is operational before submitting or managing jobs.
Practical examples:
- Before starting a batch of render jobs, use the Health Check to confirm the Nexrender server is reachable.
- Automate alerts or workflows based on the health status of the rendering service.
Properties
| Name | Meaning |
|---|---|
| Manual Assets JSON | JSON string representing assets for the job, used when overriding default assets manually. |
Note: The provided property "Manual Assets JSON" appears conditionally when the user opts to override assets manually. It expects a JSON-formatted string describing the assets involved in the rendering job.
Output
The node outputs an array of items where each item contains a json field holding the response from the Nexrender API.
For the Health Check operation, the output JSON typically includes the health status information returned by the Nexrender /health endpoint, indicating whether the service is up and running.
No binary data output is produced by this node.
Dependencies
- Requires access to a Nexrender API endpoint.
- Needs an API authentication token (provided via credentials) to authorize requests.
- The node configuration must include the domain and endpoint URL of the Nexrender server.
- Network connectivity to the Nexrender service is essential.
Troubleshooting
No credentials returned!
Occurs if the node cannot retrieve the required API authentication token. Ensure credentials are properly configured in n8n.API Response Error:
Indicates the Nexrender API responded with an error status. Check the message for details (e.g., invalid token, incorrect endpoint, or malformed request).Unknown Error:
Could be due to network issues, misconfiguration, or unexpected exceptions. Verify network access and parameter correctness.If the health check fails, verify that the Nexrender server is running and accessible at the configured domain and endpoint.