Actions42
- getUserByID
- addHumanUser
- 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 across multiple Zitadel services such as UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, and UserSchemaService. Specifically, the removePhone operation under the UserService resource is designed to remove a phone number associated with a user by their user ID.
Common scenarios for this node include managing user accounts and their attributes within Zitadel, such as updating or removing contact information like phone numbers. For example, an administrator could use this node to programmatically remove a user's phone number when it is no longer valid or needed.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. Default is UserService. |
| userId | The unique identifier of the user whose phone number will be removed. Required when Service is UserService and Operation is removePhone. |
Output
The node outputs a JSON object representing the response from the Zitadel API after performing the requested operation. For the removePhone operation, this typically includes confirmation details about the removal action 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 to communicate with Zitadel services.
Troubleshooting
- Invalid or missing API token: Ensure that the Zitadel API token is correctly set up in the node credentials; otherwise, authorization errors will occur.
- Incorrect userId: Providing an invalid or non-existent userId will result in errors or no changes. Verify the userId before running the node.
- Operation not supported: If the selected operation does not exist in the chosen service, the node returns an empty JSON object. Double-check the service-operation combination.
- JSON parsing errors: Input parameters are parsed as JSON if possible. Malformed JSON inputs can cause failures. Provide valid JSON strings or plain values accordingly.