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 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.
- Automating user deactivation workflows triggered by external systems.
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 representing the response from the Zitadel API for the deactivateUser operation. This typically includes details about the deactivated user or confirmation of the action. The exact structure depends on the Zitadel service's API response but generally contains status and metadata related to the deactivation.
No binary data output is produced by this node.
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 clients generated from Zitadel protobuf definitions to communicate with the API.
Troubleshooting
Common issues:
- Invalid or missing API token: Ensure the Zitadel API key credential is correctly set up in n8n.
- Incorrect user ID: Verify that the
userIdoridmatches an existing user in the selected service. - Service-operation mismatch: Make sure the
ServiceandOperationparameters correspond correctly; e.g., useuserIdwithUserServiceandidwithManagementService.
Error messages:
- Authorization errors: Check API token validity and permissions.
- Not found errors: Confirm the user ID exists in the specified service.
- Parsing errors: Input properties like
userIdoridmust be valid strings; avoid malformed JSON inputs.