Actions42
- listUsers
- registerTOTP
- addHumanUser
- getUserByID
- setEmail
- resendEmailCode
- verifyEmail
- setPhone
- removePhone
- resendPhoneCode
- verifyPhone
- updateHumanUser
- deactivateUser
- reactivateUser
- lockUser
- unlockUser
- deleteUser
- registerPasskey
- verifyPasskeyRegistration
- createPasskeyRegistrationLink
- listPasskeys
- removePasskey
- registerU2F
- verifyU2FRegistration
- removeU2F
- verifyTOTPRegistration
- removeTOTP
- addOTPSMS
- removeOTPSMS
- addOTPEmail
- removeOTPEmail
- startIdentityProviderIntent
- retrieveIdentityProviderIntent
- addIDPLink
- listIDPLinks
- removeIDPLink
- passwordReset
- setPassword
- listAuthenticationMethodTypes
- createInviteCode
- resendInviteCode
- verifyInviteCode
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 deleteUser operation 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 user accounts.
- 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 for the delete operation but typically includes status information about the deletion request.
No binary data output is produced by this node.
Example output JSON (simplified):
{
"details": {
"userId": "string",
"deletionStatus": "success"
}
}
(Note: Actual fields depend on Zitadel's API response.)
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
userIdproperty is provided and correctly formatted; otherwise, the API will reject the request. - Authentication errors: Verify that the Zitadel API token credential is valid and has sufficient permissions to delete users.
- Service or operation mismatch: The
deleteUseroperation only applies to theUserService. Selecting other services with this operation may cause errors or no action. - Network issues: Confirm network connectivity to the Zitadel API endpoint.
- Parsing errors: Input parameters are parsed as JSON if possible; malformed JSON inputs can cause failures.