Coolify icon

Coolify

Interact with Coolify API
Join our community

Actions36

Overview

This node integrates with the Coolify API to manage various resources, including servers. Specifically, for the Server resource with the Get Many operation, it retrieves multiple server records from the Coolify platform. This is useful when you want to list or process information about several servers managed in Coolify, such as for monitoring, reporting, or automation workflows.

Practical examples include:

  • Fetching all servers to display their status or configuration.
  • Retrieving a limited number of servers for batch processing or selective updates.
  • Integrating server data into dashboards or other systems.

Properties

Name Meaning
Return All Whether to return all server results or only up to a specified limit.
Limit The maximum number of server results to return (only applicable if "Return All" is false).

Output

The node outputs an array of JSON objects representing servers retrieved from the Coolify API. Each object contains details about a server as provided by the API. The exact structure depends on the Coolify API response but typically includes server identifiers, names, and related metadata.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the Coolify API via an API key credential configured in n8n.
  • The node uses internal helper functions to make authenticated HTTP requests to the Coolify API endpoints.
  • Network access to the Coolify API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Authentication failures due to missing or invalid API credentials.
    • Network connectivity problems preventing access to the Coolify API.
    • Request limits exceeded if too many servers are requested without pagination.

  • Error messages:

    • "The resource "server" is not implemented!" — indicates a misconfiguration or unsupported resource selection.
    • "The operation "getAll" is not implemented!" — indicates the selected operation is not available for the resource.

    To resolve these, verify that the Resource and Operation parameters are correctly set and that the node version supports them. Also, ensure valid API credentials are configured.

Links and References

Discussion