Actions72
- Image Actions
- Config Actions
- Container Actions
- Edge Group Actions
- Edge Stack Actions
- Network Actions
- Node Actions
- Registry Actions
- Secret Actions
- Service Actions
- Stack Actions
- Team Actions
- Template Actions
- User Actions
- Volume Actions
- Webhook Actions
Overview
This node integrates with the Portainer API to manage Docker Swarm secrets. Specifically, the Secret - Get Many operation retrieves a list of all Docker Swarm secrets available in a specified Portainer environment (endpoint). This is useful for users who want to programmatically access and manage secrets used by their Docker services, such as passwords, certificates, or other sensitive data stored securely within Docker Swarm.
Typical use cases include:
- Auditing or listing all secrets in a Docker Swarm environment.
- Feeding secret metadata into automation workflows.
- Synchronizing secrets information across systems.
Example: You might use this node to fetch all secrets from your production Docker Swarm environment to verify which secrets are currently deployed or to trigger updates based on secret changes.
Properties
| Name | Meaning |
|---|---|
| Environment ID | The ID of the Portainer environment/endpoint where the secrets are managed. This identifies the Docker environment to query. |
Output
The node outputs JSON data representing the list of Docker Swarm secrets retrieved from the specified environment. The output structure corresponds to the Portainer API response for secrets listing, typically an array of secret objects containing details such as secret IDs, names, creation dates, labels, and other metadata.
No binary data is output by this operation.
Dependencies
Requires a configured Portainer API credential with:
- Base URL of the Portainer instance.
- An API key token for authentication.
The node makes HTTP GET requests to the Portainer API endpoint
/endpoints/{environmentId}/docker/secretsto retrieve the secrets.Ensure that the Portainer instance is accessible from the n8n environment and that the API key has sufficient permissions to read secrets.
Troubleshooting
Common issues:
- Invalid or missing Environment ID: The node requires a valid environment ID corresponding to a Portainer endpoint.
- Authentication errors: If the API key is invalid or lacks permissions, the request will fail.
- Network connectivity: The Portainer API must be reachable from the n8n server.
Error messages:
401 Unauthorizedor403 Forbidden: Check API key validity and permissions.404 Not Found: Verify the environment ID exists in Portainer.- Timeout or connection errors: Confirm network access and correct base URL configuration.
To resolve errors, verify credentials, environment ID, and network connectivity.