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 to perform various operations on different services such as UserService, ManagementService, AuthService, and others. Specifically, for the unlockUser operation under the "Default" resource, it unlocks a user account by calling the appropriate service method in Zitadel.
Typical use cases include:
- Unlocking a user account that has been locked due to multiple failed login attempts.
- Managing user access control programmatically within an organization's identity management system.
- Automating administrative tasks related to user account status in Zitadel.
For example, an admin could use this node to unlock a user after verifying their identity or resolving security issues.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to call. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. Default is UserService. |
| userId | The unique identifier of the user to unlock. Required when Service is UserService and Operation is unlockUser. |
| id | The unique identifier used to unlock a user in the ManagementService context. Required when Service is ManagementService and Operation is unlockUser. |
Output
The node outputs a JSON object containing the response from the Zitadel API for the unlockUser operation. This typically includes details about the unlocked user or confirmation of the unlock action.
The output structure is dynamic and depends on the Zitadel API response but will be accessible in the json field of the output item.
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 API token: Ensure the Zitadel API token credential is correctly configured and valid.
- Incorrect user ID or ID parameter: Verify that the correct user identifier is provided depending on the selected service (
userIdfor UserService,idfor ManagementService). - Operation not supported: If the selected operation does not exist in the chosen service, the node returns an empty JSON object.
- JSON parsing errors: Input parameters are parsed as JSON if possible; malformed JSON strings will cause errors. Provide valid JSON or plain strings accordingly.