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-related resources, specifically here focusing on the Team resource with the Update operation. It allows users to update an existing team’s details in Portainer by specifying the team ID and new team name.
Common scenarios for this node include:
- Renaming a team within Portainer to reflect organizational changes.
- Updating team metadata as part of automated workflows managing user groups.
- Synchronizing team information from external systems into Portainer.
Example use case: You have a team called "DevOps" in Portainer, and you want to rename it to "Platform Engineering" programmatically via n8n automation.
Properties
| Name | Meaning |
|---|---|
| Team ID | The unique identifier of the team to update. This is required to specify which team will be modified. |
| Team Name | The new name to assign to the team. This is required and represents the updated team name. |
Output
The node outputs the JSON response returned by the Portainer API after updating the team. This typically includes the updated team object with its properties such as ID, name, and possibly other metadata managed by Portainer.
No binary data output is involved in this operation.
Dependencies
- Requires an active 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 configuration.
Troubleshooting
- Invalid Team ID: If the provided Team ID does not exist, the API will return an error indicating the team was not found. Verify the Team ID is correct.
- Authentication Errors: Missing or invalid API key will cause authentication failures. Ensure the API key credential is correctly configured.
- Permission Issues: The API key used must have sufficient permissions to update teams in Portainer.
- Empty or Invalid Team Name: The Team Name property is required; providing an empty string or invalid value may cause the API to reject the request.
- Network Connectivity: Ensure that the n8n instance can reach the Portainer API endpoint specified in the credentials.
Links and References
- Portainer API Documentation - Teams
- Portainer Official Website
- n8n Documentation - HTTP Request Node (for understanding API calls)
This summary is based solely on static analysis of the provided source code and input property definitions.