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
deactivateUser
AI-generatedOverview
This node integrates with the Zitadel API, allowing users to perform various operations on different Zitadel services. Specifically, for the deactivateUser operation under the "Default" resource, it deactivates a user account in the selected Zitadel service. This is useful in scenarios where administrators need to disable user access without deleting the user entirely, such as when a user leaves an organization or needs temporary suspension.
Practical examples include:
- Deactivating a user in the UserService after they leave a company.
- Temporarily disabling a user account in the ManagementService for security reasons.
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 deactivation action. The exact structure depends on the Zitadel service's API response but generally contains status and user information fields.
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 for Zitadel services.
Troubleshooting
- Invalid or missing user ID: Ensure that the
userIdoridproperty is correctly set depending on the chosen service. - Authentication errors: Verify that the API token credential is valid and has sufficient permissions.
- Operation not supported: If the selected operation does not exist for the chosen service, the node will return an empty JSON object.
- JSON parsing errors: Input properties are parsed as JSON if possible; ensure string inputs are valid JSON or plain strings as expected.