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 Zitadel services. Specifically, for the updateHumanUser operation under the default resource, it updates the details of a human user in the Zitadel 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 user contact details after a user submits a profile update form.
- Changing a user's password as part of an automated security workflow.
- Synchronizing user data from another system into Zitadel.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, use UserService. |
| userId | The unique identifier of the user to update. |
| username | The new username for the user. |
| profile | The profile information associated with the user (likely a JSON string or structured data). |
| The user's updated email address. | |
| phone | The user's updated phone number. |
| password | The new password for the user. |
All these fields are required for the updateHumanUser operation.
Output
The node outputs a single JSON object representing the response from the Zitadel API after attempting to update the human user. This JSON contains the updated user data or relevant 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, 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 authorization failures.
- Incorrect or malformed JSON in properties like
profilemay cause parsing errors. - Providing incomplete or incorrect user identifiers (
userId) will result in not found or update failure errors.
Error messages:
- Authorization errors typically indicate problems with the API token; ensure the token is valid and has sufficient permissions.
- Parsing errors when setting parameters suggest that input strings expected to be JSON are malformed; verify JSON syntax.
- API errors related to user not found or validation failures mean the provided user ID or data does not meet Zitadel's requirements.