Coolify icon

Coolify

Interact with Coolify API

Overview

This node integrates with the Coolify API to manage various resources such as applications, databases, deployments, environment variables, private keys, projects, and servers. Specifically, for the Private Key - Delete operation, it allows users to delete a private key by specifying its unique ID. This is useful in scenarios where you need to revoke or remove access credentials securely from your infrastructure managed via Coolify.

Practical examples include:

  • Removing outdated or compromised private keys from your deployment environment.
  • Cleaning up unused keys to maintain security hygiene.
  • Automating key lifecycle management within CI/CD pipelines.

Properties

Name Meaning
ID The unique identifier of the private key to be deleted. This is a required string input.

Output

The node outputs a JSON array containing the result(s) of the delete operation. Typically, this will include confirmation details or status information returned by the Coolify API about the deletion of the specified private key.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the Coolify API.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The node depends on internal helper functions that handle HTTP requests to the Coolify API endpoints.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent private key ID will likely cause the API to return an error.
    • Network connectivity problems can prevent successful communication with the Coolify API.
    • Missing or incorrect API authentication credentials will result in authorization errors.
  • Error messages:

    • "The resource "privateKey" is not implemented!" — indicates a misconfiguration or unsupported resource selection.
    • "The operation "delete" is not implemented!" — suggests the operation name might be misspelled or not supported.
    • API errors related to invalid ID or permission denied should be resolved by verifying the ID and ensuring proper API permissions.

Links and References

Discussion