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 across multiple Zitadel services. Specifically, for the removePhone operation under the default resource, it interacts with the UserService to remove a phone number associated with a user.
Common scenarios where this node is beneficial include:
- Managing user contact information programmatically within an identity and access management system.
- Automating user profile updates such as removing outdated or incorrect phone numbers.
- Integrating Zitadel user management into broader workflows that require dynamic user data modification.
For example, an organization could use this node in an automation workflow to clean up user profiles by removing phone numbers when users leave the company or change their contact details.
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 is to 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 of the removal or relevant status information returned by the UserService.
No binary data output is indicated in the source code.
Dependencies
- Requires an API authentication token (Personal Access Token) for Zitadel, provided via node credentials.
- Connects to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk. - Uses gRPC client libraries to communicate with Zitadel services.
- No additional external dependencies beyond those bundled with the node.
Troubleshooting
- Invalid or missing API token: Ensure the Zitadel API token credential is correctly configured; otherwise, authorization errors will occur.
- Incorrect userId: Providing an invalid or non-existent userId may result in errors or no changes. Verify the userId before execution.
- Operation not supported: If the selected operation does not exist in the chosen service, the node returns an empty JSON object.
- 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.