Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation deletes a specific team associated with an account. It is useful in scenarios where you need to manage organizational structures by removing teams that are no longer active or relevant. For example, if a project team has been disbanded or merged, this operation helps keep the account's team list up to date by deleting obsolete teams.

Properties

Name Meaning
Account Id Identifier of the account
Team Id Identifier of the team to be deleted

Output

The output JSON typically contains the response from the API confirming the deletion of the specified team. This may include status information or confirmation messages indicating whether the deletion was successful. The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating requests to the external service managing accounts and teams.
  • The node depends on the external API endpoint configured via credentials (base URL and authentication).
  • No additional environment variables are explicitly required beyond standard API authentication setup.

Troubleshooting

  • Common issues:
    • Invalid or missing Account Id or Team Id will cause the operation to fail.
    • Authentication errors if the API key or credentials are incorrect or expired.
    • Network connectivity problems can prevent the request from reaching the API.
  • Error messages:
    • "Team not found" indicates the provided Team Id does not exist under the given Account Id.
    • "Unauthorized" or "Authentication failed" suggests issues with the API key or credentials.
    • "Bad Request" may indicate malformed input parameters.
  • Resolutions:
    • Verify that both Account Id and Team Id are correct and correspond to existing entities.
    • Ensure the API key credential is valid and has necessary permissions.
    • Check network connectivity and API endpoint availability.

Links and References

  • Refer to the external API documentation for detailed information on the delete team endpoint.
  • Consult n8n documentation on setting up API key credentials and error handling best practices.

Discussion