Coolify icon

Coolify

Interact with Coolify API
Join our community

Actions36

Overview

This node integrates with the Coolify API to manage various resources such as servers, applications, databases, deployments, and more. Specifically, for the Server - Get operation, it retrieves detailed information about a server identified by its unique ID. This is useful in scenarios where you need to fetch server details dynamically within an automation workflow, for example, to monitor server status, retrieve configuration data, or use server metadata in subsequent steps.

Practical examples:

  • Fetching server details before deploying an application to ensure the target server meets requirements.
  • Retrieving server information to log or audit infrastructure state.
  • Using server metadata to conditionally trigger other workflows or notifications.

Properties

Name Meaning
ID The unique identifier of the server to retrieve. This is a required string input that specifies which server's details to fetch.

Output

The node outputs an array of JSON objects representing the server(s) retrieved. Each object contains the server's properties as returned by the Coolify API, such as its name, ID, status, configuration, and other metadata fields relevant to the server resource.

If the node supports binary data output (not indicated here), it would typically represent files or attachments related to the server, but this node focuses on JSON data output only.

Dependencies

  • Requires an active connection to the Coolify API via an API key credential configured in n8n.
  • The node depends on the Coolify API endpoints to fetch server data.
  • No additional external services are required beyond the Coolify API.

Troubleshooting

  • Common issues:

    • Invalid or missing server ID: The node requires a valid server ID; providing an empty or incorrect ID will cause errors.
    • API authentication failure: Ensure the API key credential is correctly set up and has sufficient permissions.
    • Network or API downtime: Connectivity issues with the Coolify API can cause request failures.

  • Error messages:

    • "The resource "server" is not implemented!" — indicates a misconfiguration or internal error; verify the resource selection.
    • "The operation "get" is not implemented!" — suggests the operation is unsupported; check the node version and resource-operation combination.
    • API errors from Coolify (e.g., 404 Not Found if the server ID does not exist) will be propagated; verify the server ID correctness.

Links and References

Discussion