Actions42
- addHumanUser
- getUserByID
- listUsers
- setEmail
- resendEmailCode
- verifyEmail
- setPhone
- removePhone
- resendPhoneCode
- verifyPhone
- updateHumanUser
- deactivateUser
- reactivateUser
- lockUser
- unlockUser
- deleteUser
- registerPasskey
- verifyPasskeyRegistration
- createPasskeyRegistrationLink
- listPasskeys
- removePasskey
- registerU2F
- verifyU2FRegistration
- removeU2F
- registerTOTP
- 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 such as UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, and UserSchemaService. The node allows performing various operations on these services by calling their respective API methods.
For the specified Resource "Default" and Operation "deleteUser", the node deletes a user from the UserService by their user ID. This is useful in scenarios where you need to programmatically remove users from your identity management system, for example, when cleaning up inactive accounts or automating user lifecycle management.
Practical examples:
- Automatically deleting users who have not logged in for a long time.
- Removing users as part of an offboarding workflow.
- Managing user data compliance by deleting user records upon request.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to use. Options: 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 output is a JSON object representing the response from the Zitadel API after attempting to delete the user. The exact structure depends on the API's response but typically includes status information about the deletion operation.
No binary data output is produced by this node.
Example output JSON (simplified):
{
"details": {
"userId": "string",
"deletionStatus": "success"
}
}
Dependencies
- Requires an API authentication token (Personal Access Token) for Zitadel, configured in the node credentials.
- Connects to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk. - Uses gRPC client libraries internally to communicate with Zitadel services.
Troubleshooting
Common issues:
- Invalid or missing API token: Ensure the Zitadel API key credential is correctly set up.
- Incorrect userId: Verify that the userId provided exists in the Zitadel UserService.
- Network connectivity problems: Confirm that the node can reach the Zitadel API endpoint.
Error messages:
- Authorization errors: Usually indicate invalid or expired API tokens; refresh or reconfigure credentials.
- Not found errors: Occur if the userId does not exist; double-check the userId value.
- Parsing errors: If input parameters are malformed JSON, ensure correct formatting.