Actions12
Overview
This node integrates with the Nexrender API to manage rendering jobs for After Effects automation. Specifically, the "Delete" operation under the "Nexrender Task" resource allows users to delete a rendering job by its unique identifier (UID). This is useful in scenarios where a job is no longer needed, has been completed, or must be removed due to errors or changes in project requirements.
Practical examples include:
- Automatically cleaning up old or failed render jobs from a queue.
- Managing job lifecycle by deleting tasks after successful completion.
- Removing test or placeholder jobs during development workflows.
Properties
| Name | Meaning |
|---|---|
| Job UID | The unique identifier (UID) of the Nexrender job to delete. |
| Manual Assets JSON | (Not applicable for Delete operation) JSON string representing assets override for the job. Required only if assetsOverride flag is true, but not relevant here. |
Note: For the Delete operation, only the Job UID property is required and used.
Output
The node outputs a JSON object representing the response from the Nexrender API after attempting to delete the specified job. Typically, this will contain confirmation of deletion or details about the deleted job. The exact structure depends on the API's response but generally includes status information.
No binary data output is produced by this node.
Example output JSON might look like:
{
"id": "job-uid",
"status": "deleted",
"message": "Job successfully deleted"
}
Dependencies
- Requires an active connection to a Nexrender server via its REST API.
- Needs an API authentication token (referred generically as an API key credential) configured in n8n credentials.
- The node uses HTTP requests to communicate with the Nexrender API endpoint defined in the credentials.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing an incorrect or non-existent Job UID will result in API errors indicating the job was not found.
- Network connectivity problems can prevent communication with the Nexrender server.
Error messages:
API Response Error: Indicates the Nexrender API returned an error response, often including details such as "Job not found" or "Unauthorized".Unknown Error: Covers unexpected issues such as network timeouts or malformed requests.
Resolutions:
- Verify that the API token is correctly set and has sufficient permissions.
- Double-check the Job UID for correctness.
- Ensure the Nexrender server URL and endpoint are reachable from the n8n environment.
Links and References
- Nexrender Official Documentation
- Nexrender API Reference
- n8n HTTP Request Node Documentation (for understanding underlying HTTP calls)