Portainer

Overview

This node integrates with the Portainer API to manage Docker-related resources. Specifically, for the Team - Get operation, it retrieves detailed information about a specific team by its ID. This is useful in scenarios where you want to fetch and use team details within an automation workflow, such as managing user permissions, auditing team configurations, or synchronizing team data with other systems.

Practical example:
You have a workflow that needs to verify the existence and details of a team before assigning users or performing further operations. Using this node's "Get Team" operation, you can retrieve the team's information by providing its ID and then branch your workflow logic based on the returned data.

Properties

Output

The node outputs JSON data representing the team object retrieved from the Portainer API. The structure typically includes all properties of the team resource as defined by Portainer, such as team name, ID, members, and any associated metadata.

No binary data output is involved in this operation.

Dependencies

• Requires connection to a Portainer instance via its API.
• Requires 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.

Troubleshooting

• Common issues:

  • Invalid or missing Team ID: The node requires a valid team ID; ensure the ID exists in Portainer.
  • Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Network connectivity: Ensure n8n can reach the Portainer API endpoint.

• Common error messages:

  • 404 Not Found: The specified team ID does not exist. Check the ID value.
  • 401 Unauthorized: Authentication failed due to invalid or missing API key. Reconfigure credentials.
  • 500 Internal Server Error: Server-side issue; retry later or check Portainer server health.

Links and References

• Portainer API Documentation
• Portainer Teams Management