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 to perform various operations on different services related to user and organization management. Specifically, for the updateHumanUser operation under the default resource, it updates details of a human user in the UserService. This is useful in scenarios where you need to programmatically modify user information such as username, profile, email, phone number, or password within an identity and access management system.
Practical examples include:
- Updating a user's contact information after they submit a profile update form.
- Changing a user's password as part of a password reset workflow.
- Modifying user attributes during onboarding or administrative updates.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, must be "UserService". |
| userId | The unique identifier of the user to update. |
| username | The new username for the user. |
| profile | The profile information string associated with the user. |
| The user's updated email address. | |
| phone | The user's updated phone number. |
| password | The new password for the user. |
All these properties are required when performing the updateHumanUser operation.
Output
The node outputs a JSON object representing the response from the Zitadel API after attempting to update the human user. This typically includes confirmation of the updated user data or any relevant metadata returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token (Personal Access Token) for Zitadel, which must be 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 missing API token will cause authentication failures.
- Providing malformed JSON strings in input fields that expect JSON may cause parsing errors.
- Missing required parameters like
userIdorusernamewill result in validation errors.
Error messages:
- Authentication errors usually indicate invalid or expired tokens; ensure the API key credential is valid.
- Parsing errors occur if input fields contain invalid JSON; verify the input format.
- API errors from Zitadel might include user not found or permission denied; check user existence and permissions.