Actions12
Overview
This node integrates with the Nexrender API to manage rendering jobs for Adobe After Effects projects. It allows users to create, update, retrieve, list, and delete rendering jobs programmatically within n8n workflows. The primary use case is automating video or animation rendering tasks by specifying project files, compositions, assets, and render settings.
Typical scenarios include:
- Automating batch rendering of After Effects projects.
- Dynamically modifying project assets before rendering.
- Managing render job priorities and tags for organization.
- Triggering custom actions at different stages of the render process (e.g., pre-download, post-render).
- Integrating rendered outputs into further workflow steps like uploading or notifications.
For example, a user can create a render job that points to a specific .aep project file, specify which composition to render, define frame ranges, and provide assets to replace in the project. After rendering, the output can be copied to a permanent location or processed further.
Properties
| Name | Meaning |
|---|---|
| AEP Project Source | Location URI of the After Effects project file (.aep) to render (e.g., file:///project.aep). |
| Composition | The composition path inside the project to render, e.g., "MainComp->PreComp->PrePreComp". |
| Continue On Missing | Boolean flag indicating whether to continue rendering if some assets are missing. |
| Workfolder Render Output Path | Temporary output path for the rendered file during processing (e.g., /folder/myrender.mov). |
| Keep Renders After Finish | Whether to keep the final rendered files after the job finishes. |
| Use Job UID As Final Render Filename | If keeping renders, whether to name the final render file using the job's unique ID. |
| Copy Final Render To (Folder) | Permanent folder path to copy the final render to (used if Use Job UID is true and Keep Renders is true). |
| Copy Final Render To (File) | Permanent file path to copy the final render to (used if Use Job UID is false and Keep Renders is true). |
| Output Module | After Effects output module preset name for the render job (default: "Lossless with Alpha"). |
| Output Extension | File extension for the output render (e.g., mov). |
| Render Settings | After Effects render settings preset name (default: "Best Settings"). |
| Starting Frame Number | Frame number to start rendering from. |
| Ending Frame Number | Frame number to end rendering on. |
| Image Sequence | Boolean indicating if the output should be an image sequence instead of a video file. |
| Render Priority | Numeric priority of the render job; lower numbers indicate higher priority. |
| Job Tags | String of tags to categorize or label the job. |
| Assets | Collection of assets to override or inject into the project. Each asset includes: type (audio, data, image, static, video), source URI, provider (e.g., file, HTTP, S3), layer identification (by name or index), property to modify, value or expression, caching options, etc. |
| Insert Manual Assets | Boolean to enable manual JSON input for assets instead of using the UI collection. |
| Manual Assets JSON | Raw JSON string defining assets manually when Insert Manual Assets is enabled. |
| Actions | Collection of render lifecycle actions to perform, categorized as pre-download, post-download, pre-render, and post-render. Each action includes a type and JSON configuration detailing the action specifics. |
Output
The node outputs the JSON response returned by the Nexrender API for the requested operation. For the "create" operation, this typically includes details about the created job such as its unique ID, status, tags, priority, template info, assets, and actions configured.
The output JSON structure corresponds directly to the Nexrender job object schema, including fields like:
uid: Unique job identifier.type: Job type.tags: Job tags.priority: Job priority.template: Template details including source, composition, frame range, and render settings.assets: List of assets associated with the job.actions: Configured actions for various render stages.stateand progress information.
If binary data is involved (e.g., rendered files), the node does not output it directly but manages file paths and copying through job configuration and actions.
Dependencies
- Requires access to a Nexrender API endpoint with proper authentication via an API token credential.
- The node expects the Nexrender server domain and endpoint URL to be configured in credentials.
- The Nexrender API must be reachable from the n8n environment.
- Optional dependencies include external storage providers referenced in asset sources (e.g., Amazon S3, Google Cloud Storage).
Troubleshooting
- No credentials returned!: Indicates missing or misconfigured API authentication credentials. Ensure the API token credential is set up correctly in n8n.
- API Response Error: Errors returned by the Nexrender API, often due to invalid parameters, missing files, or permission issues. Check the error message for details and verify all input properties, especially file paths and asset URIs.
- Unknown Error: Generic errors possibly caused by network issues or unexpected exceptions. Verify connectivity to the Nexrender server and correct API endpoint.
- Missing Assets: If
Continue On Missingis false and assets are missing or inaccessible, the job may fail. Enable this option to allow rendering to proceed despite missing assets. - Invalid JSON in Manual Assets or Actions: When using manual JSON inputs, ensure the JSON syntax is valid to avoid parsing errors.