PortainerInstall

Overview

This node operation deletes a team membership in Portainer by its unique identifier. It is useful when you want to remove a user's association with a specific team, effectively revoking their team-based permissions or access within Portainer.

Practical examples include:

• Automating cleanup of team memberships when users leave an organization.
• Managing team access dynamically based on project lifecycle or role changes.
• Integrating with HR systems to synchronize team memberships automatically.

Properties

Output

The output JSON typically contains the result of the deletion operation. This may be a confirmation message or status indicating whether the deletion was successful. No binary data output is expected for this operation.

Dependencies

• Requires an API key credential for authenticating with the Portainer API.
• The node uses the Portainer API endpoint configured via credentials, specifically targeting the /api base URL.
• The node depends on the @devlikeapro/n8n-openapi-node package and an OpenAPI specification for Portainer to build requests.

Troubleshooting

• Common issues:

  • Providing an invalid or non-existent team membership ID will likely cause the API to return an error.
  • Missing or incorrect API authentication credentials will prevent the request from succeeding.
  • Network connectivity issues to the Portainer server can cause timeouts or connection errors.

• Error messages:

  • "Not Found" or similar indicates the specified team membership ID does not exist.
  • "Unauthorized" or "Forbidden" suggests problems with API credentials or insufficient permissions.

• Resolutions:

  • Verify the team membership ID is correct and exists.
  • Ensure the API key credential is valid and has appropriate permissions.
  • Check network connectivity and Portainer server availability.

Links and References

• Portainer API Documentation
• n8n Documentation on HTTP Request Nodes (for general API interaction concepts)