Actions14
Overview
This node integrates with the Nexrender Cloud API to manage rendering jobs and related resources. Specifically, the Job Create operation allows users to submit a new rendering job by providing a detailed job payload. This is useful in automated video rendering workflows where you want to programmatically create render jobs based on dynamic input data.
Typical use cases include:
- Automating video production pipelines by submitting render jobs with custom templates and assets.
- Integrating Nexrender rendering capabilities into larger automation workflows.
- Creating jobs dynamically from user input or other system events.
For example, you might use this node to send a JSON payload describing a video composition, including template references, assets, and output settings, which Nexrender will then process asynchronously.
Properties
| Name | Meaning |
|---|---|
| Body | The JSON payload describing the job to be created. This includes all necessary details for the render job such as template, assets, actions, and output configuration. The value must be valid JSON representing the job specification. |
Output
The node outputs a JSON object representing the response from the Nexrender API after creating the job. This typically includes:
- Job ID
- Status of the job (e.g., pending)
- Details of the submitted job payload as stored by Nexrender
- Metadata such as creation timestamps
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Nexrender Cloud API.
- The base URL for the API is configurable via credentials.
- The node uses HTTP requests with JSON payloads to communicate with the Nexrender API.
Troubleshooting
- Invalid JSON in Body: If the "Body" property contains malformed JSON, the node will throw an error when parsing. Ensure the JSON is well-formed.
- Authentication Errors: If the API key or domain is incorrect or missing, requests will fail. Verify that the credential is properly configured.
- API Request Failures: Network issues or invalid job specifications can cause errors. The node surfaces HTTP status codes and error messages returned by the API.
- Operation Not Implemented: If the resource or operation parameters are incorrect, the node throws an error indicating the operation is not implemented.