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 applications and related resources. Specifically, for the Application - Create (Dockerfile) operation, it allows users to create a new application deployment based on a Dockerfile stored in a git repository. This is useful for automating deployments of containerized applications by specifying the source code repository, branch, and Dockerfile path.
Common scenarios include:
- Automating deployment pipelines where applications are built from Dockerfiles.
- Managing multiple application deployments across different servers and projects.
- Quickly setting up new applications by linking to existing git repositories containing Dockerfiles.
Example: Deploying a web app by providing its git repository URL, specifying the Dockerfile location, and selecting the target server and project within Coolify.
Properties
| Name | Meaning |
|---|---|
| Server Name or ID | Select the target server where the application will be deployed. Can choose from a list or use an expression to specify the server ID. |
| Project Name or ID | Select the project under which the application will be created. Can choose from a list or use an expression to specify the project ID. |
| Name | The name to assign to the new application. |
| Repository URL | The URL of the git repository containing the application's source code. |
| Dockerfile Path | The relative path to the Dockerfile within the repository. Defaults to ./Dockerfile. |
| Branch | The git branch to deploy from. Defaults to main. |
Output
The node outputs JSON data representing the result of the application creation request to the Coolify API. This typically includes details about the newly created application such as its ID, status, configuration, and metadata returned by the API.
If binary data were involved (not indicated here), it would represent files or artifacts related to the deployment, but this operation focuses on JSON response data only.
Dependencies
- Requires an active connection to the Coolify API via an API authentication token configured in n8n credentials.
- The node depends on the Coolify API endpoints for servers, projects, and application management.
- Network access to the Coolify service must be available.
- Git repository URLs must be accessible from the Coolify environment for cloning and building.
Troubleshooting
- Invalid Server or Project ID: If the selected server or project does not exist or is inaccessible, the API call will fail. Verify IDs and permissions.
- Repository Access Issues: Private repositories require proper access rights configured in Coolify; otherwise, cloning will fail.
- Incorrect Dockerfile Path: Specifying a wrong path to the Dockerfile will cause build failures. Ensure the path matches the repository structure.
- Branch Not Found: If the specified branch does not exist, deployment cannot proceed. Confirm branch names.
- API Authentication Errors: Missing or invalid API credentials will prevent communication with Coolify. Check credential setup in n8n.
- Network Connectivity: Ensure that n8n can reach the Coolify API endpoint without firewall or proxy issues.