Actions14
Overview
This node integrates with the Nexrender Cloud API, allowing users to manage various Nexrender resources such as jobs, templates, fonts, and secrets. Specifically for the Secret - Delete operation, it deletes a secret identified by its ID from the Nexrender service.
Common scenarios where this node is beneficial include:
- Automating the cleanup of sensitive data (secrets) stored in Nexrender.
- Managing secrets programmatically as part of a larger workflow that involves rendering jobs or template management.
- Ensuring secrets are removed when no longer needed to maintain security compliance.
Example use case:
- After completing a rendering job that required temporary credentials or tokens stored as secrets, you can use this node to delete those secrets automatically.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the secret to be deleted. This is a required field and must be provided as a string. It is treated as sensitive input (password type). |
Output
The output JSON contains the response from the Nexrender API after attempting to delete the secret. Typically, it will be an object indicating success, for example:
{
"success": true
}
If the API returns additional information, it will be included in the JSON output. No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Nexrender Cloud API.
- The node expects the base URL of the Nexrender API to be configured via credentials.
- Network access to the Nexrender API endpoint is necessary.
Troubleshooting
Common issues:
- Providing an invalid or non-existent secret ID will likely result in an error from the API.
- Missing or incorrect API authentication credentials will cause authentication failures.
- Network connectivity problems may prevent the node from reaching the Nexrender API.
Error messages:
- Errors returned by the API are captured and presented as node errors. They typically include HTTP status codes and descriptive messages.
- Timeout or network errors will also be surfaced as node errors.
Resolution tips:
- Verify the secret ID is correct and exists in your Nexrender account.
- Ensure the API key credential is valid and has appropriate permissions.
- Check network connectivity and firewall settings.
- Enable "Continue on Fail" if you want the workflow to proceed despite individual item errors.