Actions36
- Application Actions
- Database Actions
- Deployment Actions
- Environment Variable Actions
- Private Key Actions
- Project Actions
- Resource Actions
- Server Actions
Overview
This node integrates with the Coolify API to manage various resources such as applications, databases, deployments, and more. Specifically, for the Application resource with the Start operation, it triggers the start process of an application identified by its UUID. This is useful in automation workflows where you want to programmatically control the lifecycle of your applications hosted or managed via Coolify.
Practical examples:
- Automatically start an application after deployment completes.
- Schedule application startups based on external events or triggers.
- Integrate application start commands into CI/CD pipelines.
Properties
| Name | Meaning |
|---|---|
| Application ID | UUID of the application to start |
The node requires the unique identifier (UUID) of the application to perform the start operation.
Output
The node outputs a JSON array containing the response from the Coolify API related to the start operation of the application. The exact structure depends on the API's response but typically includes status information about the start request.
No binary data output is involved.
Dependencies
- Requires an active connection to the Coolify API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node uses internal helper functions to make HTTP requests to Coolify endpoints.
Troubleshooting
Common issues:
- Invalid or missing Application ID (UUID) will cause the operation to fail.
- Network connectivity problems can prevent communication with the Coolify API.
- Insufficient permissions or invalid API credentials will result in authorization errors.
Error messages:
"The resource "application" is not implemented!"— indicates a misconfiguration or unsupported resource selection."The operation "start" is not implemented!"— suggests the operation name might be incorrect or not supported.- API errors returned from Coolify (e.g., 401 Unauthorized, 404 Not Found) should be checked and resolved by verifying credentials and application existence.
Links and References
- Coolify Official Documentation (for API details and application management)
- n8n Documentation (for general node usage and credential setup)