Actions72
- Image Actions
- Network Actions
- Node Actions
- Registry Actions
- Secret Actions
- Service Actions
- Stack Actions
- Team Actions
- Template Actions
- User Actions
- Volume Actions
- Webhook Actions
- Config Actions
- Container Actions
- Edge Group Actions
- Edge Stack Actions
Overview
The node integrates with the Portainer API to manage Docker environments, specifically allowing control over Docker containers, images, volumes, networks, stacks, and other Docker resources. For the Container - Start operation, it enables users to start a stopped Docker container within a specified environment (endpoint) managed by Portainer.
This operation is useful in scenarios where automated workflows need to programmatically start containers after maintenance, deployment, or based on external triggers. For example, you might use this node to start a web server container after updating its image or to resume a paused service as part of a recovery process.
Properties
| Name | Meaning |
|---|---|
| Environment ID | The ID of the Portainer environment/endpoint where the container resides. |
| Container ID | The unique identifier of the Docker container to be started. |
Output
- The output JSON contains the response from the Portainer API after attempting to start the container.
- Typically, for a start operation, the API returns an empty body with HTTP status indicating success or failure.
- No binary data is produced by this operation.
Dependencies
- Requires a configured Portainer API credential with:
- Base URL of the Portainer instance.
- An API key for authentication.
- The node sends authenticated HTTP POST requests to the Portainer API endpoint corresponding to the container start action.
Troubleshooting
Common issues:
- Invalid or missing Environment ID or Container ID will cause the API call to fail.
- Insufficient permissions or invalid API key may result in authorization errors.
- Attempting to start a container that is already running may return an error or no effect.
- Network connectivity issues between n8n and the Portainer server can cause request failures.
Error messages and resolutions:
- 401 Unauthorized: Check that the API key credential is correct and has sufficient permissions.
- 404 Not Found: Verify that the Environment ID and Container ID are valid and exist in Portainer.
- 409 Conflict: The container might already be running; confirm container state before starting.
- Timeouts or network errors: Ensure the Portainer server is reachable from n8n.
Links and References
- Portainer API Documentation - Containers
- Docker Engine API - Start Container (Portainer uses Docker API under the hood)
- Portainer Official Website