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 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 | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. Default is UserService. |
| userId | The unique identifier of the user to deactivate (required when Service is UserService and Operation is deactivateUser). |
| id | The unique identifier of the user to deactivate (required when Service is ManagementService and Operation is deactivateUser). |
Output
The node outputs a JSON object containing the response from the Zitadel API for the deactivateUser operation. The exact structure depends on the service's API response but generally includes confirmation of the deactivation action or relevant status information.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token credential for Zitadel (referred generically as "an API key credential").
- Connects to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk. - Uses gRPC client libraries internally to communicate with Zitadel services.
Troubleshooting
Common issues:
- Missing or invalid API authentication token will cause authorization failures.
- Providing incorrect or missing user identifiers (
userIdorid) will result in errors from the Zitadel API. - Selecting a service-operation combination without required parameters may lead to incomplete requests.
Error messages:
- Authorization errors typically indicate problems with the provided API token; ensure the token is valid and has sufficient permissions.
- Validation errors from Zitadel usually specify which parameter is missing or malformed; verify that the correct user ID field is set according to the chosen service.
- Network or connectivity errors suggest issues reaching the Zitadel API endpoint; check network settings and endpoint availability.
Links and References
- Zitadel Official Documentation
- Zitadel API Reference (for detailed API method descriptions)