Actions190
- Auth Actions
- Backup Actions
- Custom Templates Actions
- Docker Actions
- Edge Groups Actions
- Edge Jobs Actions
- Edge Stacks Actions
- Endpoint Groups Actions
- Endpoints Actions
- Endpoint Delete Batch
- Endpoint List
- Endpoint Create
- Endpoint Delete
- Endpoint Inspect
- Endpoint Update
- Endpoint Association Delete
- Endpoint Dockerhub Status
- Endpoint Edge Status Inspect
- Endpoint Force Update Service
- Endpoint Registries List
- Endpoint Registry Access
- Endpoint Settings Update
- Endpoint Snapshot
- Endpoint Update Relations
- Gitops Actions
- Helm Actions
- Intel Actions
- Kubernetes Actions
- Get All Kubernetes Applications
- Get All Kubernetes Applications Count
- Delete Cluster Role Bindings
- Delete Cluster Roles
- Get All Kubernetes Cluster Role Bindings
- Get All Kubernetes Cluster Roles
- Get All Kubernetes Config Maps
- Get All Kubernetes Config Maps Count
- Get Kubernetes Cron Jobs
- Delete Cron Jobs
- Get Kubernetes Dashboard
- Get All Kubernetes Ingress Controllers
- Update Kubernetes Ingress Controllers
- Get All Kubernetes Cluster Ingresses
- Get All Kubernetes Cluster Ingresses Count
- Delete Kubernetes Ingresses
- Get Kubernetes Jobs
- Delete Jobs
- Get Kubernetes Max Resource Limits
- Get Applications Resources
- Get Kubernetes Metrics For All Nodes
- Get Kubernetes Metrics For Node
- Get Kubernetes Metrics For All Pods
- Get Kubernetes Metrics For Pod
- Delete Kubernetes Namespace
- Get Kubernetes Namespaces
- Create Kubernetes Namespace
- Update Kubernetes Namespace Deprecated
- Get Kubernetes Namespace
- Update Kubernetes Namespace
- Get Kubernetes Config Map
- Get Kubernetes Ingress Controllers By Namespace
- Update Kubernetes Ingress Controllers By Namespace
- Get All Kubernetes Ingresses
- Create Kubernetes Ingress
- Update Kubernetes Ingress
- Get Kubernetes Ingress
- Get Kubernetes Secret
- Get Kubernetes Services By Namespace
- Create Kubernetes Service
- Update Kubernetes Service
- Kubernetes Namespaces Toggle System
- Get Kubernetes Volumes In Namespace
- Get Kubernetes Namespaces Count
- Get Kubernetes Nodes Limits
- Get Kubernetes RBAC Status
- Delete Role Bindings
- Get Kubernetes Role Bindings
- Get Kubernetes Roles
- Delete Roles
- Get Kubernetes Secrets
- Get Kubernetes Secrets Count
- Delete Service Accounts
- Get Kubernetes Service Accounts
- Get Kubernetes Services
- Get All Kubernetes Services Count
- Delete Kubernetes Services
- Get All Kubernetes Volumes
- Get Kubernetes Volume
- Get All Kubernetes Volumes Count
- Get Kubernetes Config
- Ldap Actions
- Registries Actions
- Resource Controls Actions
- Settings Actions
- Ssl Actions
- Stacks Actions
- Stack List
- Stack Delete
- Stack Inspect
- Stack Update
- Stack Associate
- Stack File Inspect
- Stack Update Git
- Stack Git Redeploy
- Stack Migrate
- Stack Start
- Stack Stop
- Stack Create Kubernetes Git
- Stack Create Kubernetes File
- Stack Create Kubernetes Url
- Stack Create Docker Standalone File
- Stack Create Docker Standalone Repository
- Stack Create Docker Standalone String
- Stack Create Docker Swarm File
- Stack Create Docker Swarm Repository
- Stack Create Docker Swarm String
- Stack Delete Kubernetes By Name
- Webhook Invoke
- Tags Actions
- Team Memberships Actions
- Teams Actions
- Templates Actions
- Upload Actions
- Users Actions
Stacks → Stack Git Redeploy
AI-generatedOverview
The "Stack Git Redeploy" operation for the "Stacks" resource allows users to trigger a redeployment of a stack by pulling updated Git configurations. This is useful in scenarios where infrastructure or application stacks managed via Portainer need to be updated automatically based on changes in their Git repositories. For example, after pushing new code or configuration changes to a Git repository, this node can pull those changes and redeploy the stack accordingly, ensuring that the running environment reflects the latest updates.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the stack to redeploy. |
| Body | A JSON string containing Git configuration details for pulling and redeploying the stack. For Kubernetes stacks, the StackName field may be included; if set as an empty string, it will clear the name. |
| Additional Fields | Optional extra parameters: - Endpoint Id: For stacks created before version 1.18.0 that might lack an associated environment (endpoint) ID, this number sets the environment ID used by the stack. |
Output
The node outputs JSON data representing the response from the Portainer API after attempting the Git redeploy operation on the specified stack. This typically includes status information about the redeployment process, success confirmation, or error details if the operation failed.
No binary data output is expected from this node.
Dependencies
- Requires an active connection to a Portainer instance via its API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL of the Portainer API must be provided in the credentials.
- The node uses HTTP requests with JSON payloads to interact with the Portainer API.
Troubleshooting
Common Issues:
- Invalid or missing stack ID: Ensure the stack identifier is correct and exists in Portainer.
- Incorrect or malformed Git configuration JSON in the Body property: Validate the JSON format and required fields.
- Missing or invalid API credentials: Verify that the API key/token and base URL are correctly configured.
- Endpoint ID mismatch for older stacks: If redeploy fails due to environment issues, try specifying the Endpoint Id in Additional Fields.
Error Messages:
- Authentication errors usually indicate invalid or expired API credentials.
- 404 Not Found errors suggest the stack ID does not exist or is inaccessible.
- 400 Bad Request errors often mean the Git config body is improperly formatted or missing required fields.
Resolving these generally involves verifying input parameters, checking API credentials, and confirming the stack's existence and state in Portainer.