Coolify icon

Coolify

Interact with Coolify API
Join our community

Actions36

Overview

This node integrates with the Coolify API to perform various operations on different resources such as applications, databases, deployments, and more. Specifically, for the Database - Get operation, it retrieves detailed information about a specific database by its ID. This is useful in scenarios where you need to fetch database metadata or configuration details programmatically within an n8n workflow.

Practical examples include:

  • Automatically retrieving database connection details before running queries.
  • Fetching database status or properties to monitor or audit databases.
  • Integrating database info retrieval into deployment or backup workflows.

Properties

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

Output

The node outputs an array of JSON objects representing the retrieved database(s). For the "Get" operation on a database resource, the output JSON contains the detailed information of the specified database identified by the provided ID. The exact structure depends on the Coolify API response but typically includes fields like database name, type, host, port, credentials (masked or partial), and other metadata.

No binary data output is indicated for 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.
  • No additional external dependencies beyond the Coolify API and proper credential setup.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent database ID will likely result in an error or empty response.
    • Missing or incorrect API credentials will cause authentication failures.
    • Network connectivity issues to the Coolify API endpoint can prevent successful execution.

  • Error messages:

    • "The resource "database" is not implemented!" — indicates a misconfiguration or missing resource implementation; unlikely if using standard node.
    • "The operation "get" is not implemented!" — suggests the operation name is incorrect or unsupported.
    • Authentication errors usually indicate invalid or missing API keys; verify credentials in n8n.
    • API request failures may return HTTP error codes; check network and API status.

To resolve errors, ensure the database ID is correct, credentials are valid, and the Coolify API service is reachable.

Links and References

Discussion