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 interacts with the Zitadel API to perform various operations across multiple 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 with the provided user identifier.
Common scenarios where this node is beneficial include:
- Automating user management tasks like unlocking locked user accounts.
- Integrating Zitadel user administration into workflows without manual intervention.
- Managing users programmatically in identity and access management systems.
For example, an admin could use this node to automatically unlock a user after verifying their identity or resolving an issue, streamlining support processes.
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. 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 invoked operation. For the unlockUser operation, this typically includes confirmation details about the unlocked user or status information returned by the API.
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's protobuf definitions to communicate with the API.
Troubleshooting
- Invalid or missing API token: Ensure that the Zitadel API token credential is correctly set up and has sufficient permissions.
- Incorrect user ID: Verify that the
userIdoridproperty matches an existing user in the Zitadel system. - Operation not found: If the selected operation does not exist for the chosen service, the node will return an empty JSON object.
- JSON parsing errors: Input properties that expect JSON strings must be valid JSON; otherwise, the node falls back to treating them as plain strings.