Actions14
Overview
This node interacts with the Nexrender Cloud API to manage fonts among other resources. Specifically, for the Font Delete operation, it deletes a font resource identified by its unique ID from the Nexrender system. This is useful in scenarios where you want to programmatically remove unused or obsolete fonts from your Nexrender account to keep your environment clean and organized.
Practical examples include:
- Automating cleanup of fonts after rendering jobs complete.
- Managing font lifecycle in bulk workflows.
- Integrating font management into larger video rendering pipelines.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the font to delete. This is required to specify which font resource should be removed. |
Output
The output JSON contains the response from the Nexrender API after attempting to delete the font. Typically, this will be an object indicating success or failure of the deletion request. For example, a successful deletion might return:
{
"success": true
}
If the API returns additional data, it will be included in the JSON output as well.
The node does not output binary data for 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 (defaulting to
https://api.nexrender.com/api/v2). - The node uses HTTP DELETE requests to the
/fonts/{fontId}endpoint.
Troubleshooting
Common issues:
- Providing an invalid or non-existent font ID will likely result in an error from the API.
- Network connectivity problems or incorrect API credentials can cause authentication failures.
- Attempting to delete a font that is currently in use by active jobs may be rejected by the API.
Error messages:
- Errors returned by the API are captured and presented as node errors with messages including HTTP status codes and error details.
- A typical error message might look like:
HTTP 404: Font not foundif the font ID does not exist. - To resolve errors, verify the font ID, ensure valid API credentials, and check network connectivity.