Actions14
Overview
The node integrates with the Nexrender Cloud API, specifically enabling users to create rendering jobs programmatically. This is useful in scenarios where automated video or animation rendering workflows are needed, such as generating personalized videos, batch processing animations, or integrating rendering tasks into larger automation pipelines.
For the Job Create operation, the node sends a job creation payload to the Nexrender API, which then schedules and processes the rendering job on the cloud service. Users provide the job details in JSON format, defining templates, assets, and output settings.
Practical Example
- Automate the creation of multiple video render jobs by feeding different JSON payloads describing each job.
- Integrate with other systems to trigger video rendering dynamically based on user input or events.
Properties
| Name | Meaning |
|---|---|
| Body | The JSON payload describing the job to be created. This includes all necessary parameters for the Nexrender API to schedule and process the rendering job. The payload must conform to Nexrender's job specification format. |
Output
The node outputs the JSON response from the Nexrender API after creating the job. This typically includes details about the newly created job such as its ID, status, creation timestamp, and any metadata returned by the API.
The output structure is:
{
"json": {
// Nexrender job object fields, e.g.:
"id": "string",
"status": "string",
"createdAt": "string",
"meta": { /* additional metadata */ },
...
}
}
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Nexrender Cloud API.
- Needs an API authentication token configured in n8n credentials (referred generically as "an API key credential").
- The base URL for the API is taken from the credential configuration.
- The node uses HTTP POST requests with JSON bodies to communicate with the Nexrender API.
Troubleshooting
- Invalid JSON in Body property: If the provided job payload is not valid JSON, the node will throw a parsing error. Ensure the JSON is well-formed.
- API Authentication errors: If the API key or domain is misconfigured or missing, the node will fail to authenticate. Verify that the API credentials are correctly set up.
- API request failures: Network issues or invalid job payloads can cause the API to return errors. The node surfaces these errors with HTTP status codes and messages. Review the error message for details.
- Operation not implemented error: This indicates a mismatch between resource and operation parameters. Confirm that the Resource is set to "Job" and Operation to "Create".
- Timeouts or slow responses: Since this operation only creates a job and does not wait for completion, timeouts are unlikely here but may occur if the API is unresponsive.