Zitadel icon

Zitadel

Interact with the Zitadel API

deleteUser

AI-generated

Overview

This node provides an interface to interact with the Zitadel API, a platform for identity and access management. It supports multiple services within Zitadel, such as user management, organization management, authentication, administration, and custom actions.

The specific operation deleteUser under the UserService resource allows deleting a user by their user ID. This is useful in scenarios where you need to programmatically remove users from your system, for example:

  • Cleaning up test or inactive users.
  • Automating user lifecycle management workflows.
  • Integrating user deletion into broader administrative processes.

Properties

Name Meaning
Service The Zitadel service to use. Options include: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. Default is UserService.
userId The unique identifier of the user to delete. Required when Service is UserService and Operation is deleteUser.

Output

The node outputs a JSON object representing the response from the Zitadel API after attempting to delete the user. The exact structure depends on the Zitadel API's response but typically includes status information about the deletion request.

No binary data output is produced by this node.

Example output JSON (simplified):

{
  "result": "success",
  "details": {
    "userId": "string",
    "deleted": true
  }
}

Dependencies

  • Requires an API authentication token (Personal Access Token) for Zitadel, configured in n8n credentials.
  • Connects to the Zitadel API endpoint at https://zitadel.studentcouncil.dk.
  • Uses gRPC client libraries internally to communicate with Zitadel services.

Troubleshooting

  • Invalid or missing userId: Ensure the userId property is provided and correctly formatted when using the deleteUser operation.
  • Authentication errors: Verify that the API token credential is valid and has sufficient permissions to delete users.
  • Operation not found: If the selected operation does not exist for the chosen service, the node returns an empty JSON object.
  • JSON parsing errors: Input parameters are parsed as JSON if possible; malformed JSON inputs will cause errors. Provide plain strings or valid JSON.

Links and References

Discussion