Actions14
Overview
This node integrates with the Nexrender Cloud API, enabling automation of rendering jobs and management of related resources such as jobs, templates, fonts, and secrets. Specifically, for the Secret - Create operation, it allows users to securely store a secret (a key-value pair) in the Nexrender system. This is useful when you need to manage sensitive data like API keys, passwords, or tokens that your rendering jobs might require.
Practical examples include:
- Storing an API key as a secret to be used by rendering jobs.
- Managing credentials or configuration values securely within Nexrender.
- Automating secret creation as part of a larger workflow that prepares rendering jobs.
Properties
| Name | Meaning |
|---|---|
| Name | The name or key identifier of the secret to create. This is how the secret will be referenced. |
| Value | The secret's value. This is the sensitive data stored securely. It is treated as a password field, so input is masked. |
Output
The output JSON contains the response from the Nexrender API after creating the secret. Typically, this includes a success confirmation and possibly metadata about the created secret. The exact structure depends on the API but generally confirms that the secret was stored successfully.
No binary data output is involved in this operation.
Example output snippet (conceptual):
{
"success": true,
"name": "my-secret-name",
"value": "****"
}
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 Cloud API endpoint is necessary.
Troubleshooting
Common issues:
- Missing or invalid API authentication token can cause authorization errors.
- Providing empty or invalid secret name or value will likely result in validation errors.
- Network connectivity problems may cause request failures.
Error messages:
- Errors returned from the API are parsed and presented with HTTP status codes and error details.
- Timeout or network errors will indicate inability to reach the Nexrender service.
- If the node throws an error about missing binary data, it indicates incorrect property usage (not applicable for secret creation).
Resolutions:
- Ensure the API key credential is correctly set up and has permissions to manage secrets.
- Verify that the secret name and value fields are properly filled.
- Check network connectivity and Nexrender service availability.