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, for the setPassword operation under the default resource, it enables updating a user's password by providing the current password, a new password, and a verification code. This is useful in scenarios where an administrator or user needs to securely change their password within the Zitadel identity management system.
Practical examples include:
- Resetting a user's password after verifying their identity.
- Allowing users to update their passwords as part of a security policy enforcement.
- Automating password changes during user onboarding or offboarding processes.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, "UserService" is used. |
| userId | The unique identifier of the user whose password is being changed. |
| newPassword | The new password to set for the user. |
| currentPassword | The current password of the user, required to authorize the password change. |
| verificationCode | A verification code to confirm the password change request, typically sent to the user via email or SMS. |
Output
The node outputs a JSON object representing the response from the Zitadel API for the setPassword operation. This typically includes confirmation details about the password update. The exact structure depends on the Zitadel API response but generally confirms success or provides error information.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token (Personal Access Token) for Zitadel, configured in the node credentials.
- Connects to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk. - Uses gRPC client libraries internally to communicate with Zitadel services.
Troubleshooting
Common issues:
- Invalid or expired API token: Ensure the API key credential is valid and has sufficient permissions.
- Incorrect
userId: Verify that the user ID exists in the Zitadel system. - Wrong current password or verification code: Confirm these values are correct; otherwise, the password change will be rejected.
- Network connectivity problems: Check network access to the Zitadel API endpoint.
Error messages:
- Authorization errors usually indicate invalid or missing API credentials.
- Validation errors may occur if required fields like
newPassword,currentPassword, orverificationCodeare missing or malformed. - API errors related to user state or permissions should be resolved by checking user existence and roles in Zitadel.