Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation deletes a team member from a specified team within a group. It is useful in scenarios where you need to manage team memberships dynamically, such as removing users who no longer require access or have left the organization. For example, an admin can automate the removal of a user from a project team when their role changes or they leave the company.

Properties

Name Meaning
Group Id Identifier of the Group from which the team member will be removed.
Team Id Identifier of the specific team within the group where the member belongs.
Member Id Identifier of the member (userId) to be deleted from the team.

Output

The output JSON typically contains the response from the API confirming the deletion of the team member. This may include status information or confirmation details. The node does not output binary data.

Dependencies

  • Requires an API key credential for authentication with the external service managing groups and teams.
  • The base URL for the API must be configured in the node credentials.
  • The node depends on the external API endpoint that supports deleting a team member by group ID, team ID, and member ID.

Troubleshooting

  • Common issues:

    • Invalid or missing identifiers (Group Id, Team Id, Member Id) will cause the operation to fail.
    • Authentication errors if the API key or credentials are incorrect or expired.
    • Network or connectivity issues preventing communication with the API.
  • Error messages:

    • "Not Found" or similar indicates that the specified group, team, or member does not exist.
    • "Unauthorized" or "Forbidden" suggests problems with API credentials or permissions.
  • Resolution:

    • Verify all IDs are correct and correspond to existing entities.
    • Ensure the API key credential is valid and has sufficient permissions.
    • Check network connectivity and API endpoint availability.

Links and References

  • Refer to the external API documentation for managing groups and teams for detailed information on required parameters and expected responses.
  • n8n documentation on using API key credentials and configuring HTTP request nodes may also be helpful.

Discussion