Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Group Teams → Update Member Role Within A Team

AI-generated

Overview

This node operation updates the roles assigned to a specific member within a team of a group. It is useful in scenarios where you need to manage user permissions dynamically, such as promoting a team member to an admin role or restricting access by changing their roles. For example, in a corporate environment, when a team member’s responsibilities change, this node can update their roles accordingly without manual intervention.

Properties

Name Meaning
Group Id Identifier of the Group to which the team belongs.
Team Id Identifier of the specific team within the group.
Member Id Identifier of the member (user) whose roles are being updated.
Roles JSON array specifying the roles granted to the team member. Example: ["admin","user"]

Output

The node outputs JSON data representing the result of the update operation. This typically includes confirmation of the updated member roles and possibly the updated member object or status from the API response. The exact structure depends on the external service's API but generally confirms success or failure of the role update.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the external service managing groups and teams.
  • The node uses a base URL configured in credentials to send HTTP requests.
  • The operation sends a JSON body containing the roles to update the member’s permissions.

Troubleshooting

  • Missing or invalid identifiers: Ensure that Group Id, Team Id, and Member Id are correctly provided and correspond to existing entities; otherwise, the API will return errors.
  • Invalid roles format: The Roles property must be a valid JSON array. Malformed JSON or unsupported role names may cause request failures.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions to update team member roles.
  • API endpoint issues: If the base URL or network connectivity is incorrect, the node will fail to reach the service.

Common error messages might include:

  • "Member not found" — check the Member Id.
  • "Unauthorized" — verify API credentials.
  • "Invalid roles format" — ensure the roles JSON is properly structured.

Links and References

  • Refer to the external service’s API documentation for details on roles and team management endpoints.
  • n8n documentation on how to configure API credentials and use JSON input properties.

Discussion