Actions65
- Auth Actions
- License Actions
- Monitor Actions
- Project Actions
- Service Actions
- Create
- Create from Template
- Create from Schema
- Delete
- Deploy
- Disable
- Enable
- Expose Service
- Get
- Get Logs
- Get Stats
- Refresh Deploy Token
- Restart
- Update Backup
- Update Basic Auth
- Update Build
- Update Deploy
- Update Domains
- Update Environment
- Update Health Check
- Update Mounts
- Update Ports
- Update Redirects
- Update Resources
- Update Source - Docker Image
- Update Source - Git
- Update Source - GitHub
- Settings Actions
- Change Credentials
- Get GitHub Token
- Get Let's Encrypt Email
- Get Panel Domain
- Get Server IP
- Get Status
- Get Traefik Custom Config
- Prune Docker Builder
- Prune Docker Images
- Refresh Server IP
- Restart Easypanel
- Restart Traefik
- Set Docker Prune Daily
- Set GitHub Token
- Set Let's Encrypt Email
- Set Panel Domain
- Update Traefik Custom Config
- Template Actions
- User Actions
Service → Update Build
AI-generatedSummary
Update the build configuration for an existing Easypanel service by choosing a build method and its context; Dockerfile builds also include a Dockerfile path.
Inputs
- Service Type — Select the service type: App (default), MariaDB, MongoDB, MySQL, PostgreSQL, or Redis. The selected type determines which Easypanel service update endpoint is called.
- Project Name (required) — Name of the project containing the service.
- Service Name (required) — Name of the existing service to update.
- Build Type — Choose Dockerfile (default), Heroku Buildpacks, Nixpacks, or Paketo Buildpacks.
- Dockerfile Path — Dockerfile path relative to the build context; used only for Dockerfile builds. Defaults to ./Dockerfile.
- Build Context — Build context directory, passed for every build type. Defaults to .
Output shape
A list of one n8n item per input item, each containing the API response in its json field.
Sends a request to update the selected service’s build configuration. The response data is the Easypanel tRPC result with its response wrapper removed when recognized; on failure, the node throws an error unless Continue On Fail is enabled, in which case the item contains error details.
Examples
Example 1: Configure a service to build from Nixpacks using the repository root as context.
Select Nixpacks and leave Build Context as .; Dockerfile Path is not used.