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 programmatically, such as removing obsolete or disbanded teams from an account management system. For example, if a project team is dissolved, this operation can be used to clean up the account by deleting that team's record.

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 authentication with the external service managing accounts and teams.
  • The node depends on a REST API endpoint that supports deleting teams by their identifiers.
  • Proper configuration of the base URL and authentication credentials in n8n is necessary for the node to function correctly.

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 preventing access to the API endpoint.
  • 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 credentials.
    • "Bad Request" may indicate malformed input parameters.
  • Resolutions:
    • Verify that both Account Id and Team Id are correct and exist.
    • Check and update API credentials if necessary.
    • Ensure network connectivity and correct API base URL configuration.

Links and References

  • Refer to the external API documentation for details on the delete team endpoint.
  • n8n documentation on setting up API credentials and HTTP request nodes for further customization.

Discussion