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 provides an interface to interact with the Zitadel API, a platform for identity and access management. It supports multiple services such as UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, and UserSchemaService. The specific operation removeOTPSMS under the UserService resource allows removing or disabling OTP (One-Time Password) SMS authentication for a user identified by their user ID.
Common scenarios where this node is beneficial include:
- Managing user authentication methods programmatically.
- Disabling SMS-based OTP for users who switch to other 2FA methods.
- Automating user security settings in bulk or as part of workflows.
Example use case:
- An admin wants to revoke SMS OTP for a user after they enroll in a hardware token or authenticator app. This node can be used to call the appropriate API method to remove the SMS OTP factor.
Properties
| Name | Meaning |
|---|---|
| Service | Selects which Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. Default is UserService. |
| userId | The unique identifier of the user for whom the OTP SMS should be removed. Required when Service is UserService and Operation is removeOTPSMS. |
Output
The node outputs a JSON object representing the response from the Zitadel API for the invoked operation. For the removeOTPSMS operation, the output JSON will contain the result of the removal request, typically including status information or confirmation details returned by the API.
No binary data output is produced by this node.
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 internally to communicate with Zitadel services.
Troubleshooting
- Invalid or missing API token: Ensure that the Zitadel API token credential is correctly configured and has sufficient permissions.
- Incorrect userId: Verify that the
userIdparameter is correct and corresponds to an existing user in Zitadel. - Operation not found: If the selected operation does not exist for 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 strings may cause errors. Provide valid JSON or plain strings as required.