Actions42
- getUserByID
- addHumanUser
- 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 integrates with the Zitadel API, allowing users to perform various operations on different Zitadel services. Specifically, the deactivateUser operation disables a user account in the selected service. This is useful for managing user lifecycle events such as suspending access when an employee leaves an organization or temporarily disabling accounts for security reasons.
Practical examples:
- Deactivating a user in the UserService after they leave a company.
- Disabling a user account in the ManagementService for administrative control.
Properties
| Name | Meaning |
|---|---|
| Service | Selects which Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService |
| userId | The unique identifier of the user to deactivate (used when Service is UserService and Operation is deactivateUser) |
| id | The unique identifier of the user to deactivate (used when Service is ManagementService and Operation is deactivateUser) |
Output
The node outputs a JSON object representing the response from the Zitadel API for the deactivateUser operation. This typically contains details about the deactivation result, such as confirmation status or metadata related to the user state after deactivation.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token (Personal Access Token) for Zitadel, provided via node 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 user ID: Ensure that the correct user identifier (
userIdorid) is provided depending on the selected service. - Authentication errors: Verify that the API token credential is correctly configured and has sufficient permissions.
- Operation not found: Confirm that the selected operation matches the supported methods for the chosen service.
- JSON parsing errors: Input parameters are parsed as JSON if possible; ensure string inputs are valid JSON or plain strings as expected.