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
This node integrates with the Portainer API to manage Docker Swarm configurations and other Docker-related resources. Specifically, for the Config resource with the Get Many operation, it retrieves a list of Docker Swarm configs available in a specified Portainer environment (endpoint). This is useful for users who want to programmatically access all configuration objects managed by Docker Swarm through Portainer, enabling automation of config management tasks such as auditing, reporting, or further processing.
Practical examples:
- Automatically fetching all Docker Swarm configs before deploying or updating services.
- Integrating with CI/CD pipelines to verify existing configs.
- Monitoring or backing up current Docker Swarm configs.
Properties
| Name | Meaning |
|---|---|
| Environment ID | The ID of the Portainer environment/endpoint where the Docker Swarm configs are located. |
Output
The node outputs JSON data containing an array of Docker Swarm config objects retrieved from the specified environment. Each object represents a config with its details as provided by the Portainer API.
The output structure corresponds directly to the API response for listing configs, typically including fields such as config ID, name, labels, creation date, and other metadata.
No binary data output is involved in this operation.
Dependencies
- Requires connection to a Portainer instance with API access.
- Needs an API key credential configured in n8n to authenticate requests to the Portainer API.
- The base URL of the Portainer API must be set in the credentials.
- The node uses HTTP GET requests to the endpoint
/endpoints/{environmentId}/docker/configsto fetch the configs.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Incorrect Environment ID may result in "not found" errors or empty results.
- Network connectivity problems between n8n and the Portainer server can cause request timeouts or connection errors.
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 corresponds to an existing Portainer endpoint.
- Timeout or network error: Ensure that the Portainer server is reachable from the n8n instance.