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 Start
AI-generatedOverview
This node operation, Stack Start, is designed to start a specific stack within an environment in Portainer. Portainer is a management tool for containerized environments, and stacks represent groups of services or containers defined by a compose file or similar configuration.
Typical use cases include:
- Automating the deployment lifecycle by programmatically starting stacks after updates or maintenance.
- Integrating stack control into broader workflows that manage container environments.
- Triggering stack startups based on external events or schedules.
For example, you might use this node to start a development stack automatically when a new feature branch is deployed or to restart a production stack after applying configuration changes.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the stack to be started. |
| Endpoint Id | The identifier of the environment (endpoint) where the stack resides. |
Output
The node outputs JSON data representing the response from the Portainer API after attempting to start the specified stack. This typically includes status information about the stack start operation, such as success confirmation or error details.
No binary data output is involved in this operation.
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 for the Portainer API must be set in the node credentials.
- The node uses HTTP headers specifying JSON content type and expects JSON responses.
Troubleshooting
Common issues:
- Invalid or missing stack ID or endpoint ID will cause the operation to fail.
- Authentication errors if the API key or token is incorrect or expired.
- Network connectivity problems between n8n and the Portainer server.
- Insufficient permissions for the API user to start stacks.
Error messages:
- "Unauthorized" or "Authentication failed": Check API credentials and permissions.
- "Stack not found": Verify the stack ID is correct and exists in the specified environment.
- "Endpoint not found": Confirm the endpoint ID corresponds to a valid environment.
- Timeout or network errors: Ensure the Portainer server is reachable from n8n.
Resolving these usually involves verifying input parameters, checking credential validity, and ensuring network access.
Links and References
- Portainer API Documentation
- Portainer Stacks Management
- n8n Documentation on HTTP Request Node (for understanding API calls)