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 such as UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, and UserSchemaService. Specifically, for the addOTPSMS operation under the UserService resource, it enables adding an OTP (One-Time Password) SMS for a user identified by their user ID.
Common scenarios include automating user authentication workflows where OTP via SMS is required, managing user accounts, or interacting with organizational data within Zitadel. For example, you might use this node to trigger sending an OTP SMS to a user during a login or verification process.
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 for whom the OTP SMS will be added. Required when Service is UserService and Operation is addOTPSMS. |
Output
The node outputs a JSON object representing the response from the Zitadel API for the invoked operation. For the addOTPSMS operation, this typically includes confirmation details about the OTP SMS addition, such as status or metadata returned by the API.
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 (
nice-grpc) to communicate with Zitadel services. - The node dynamically constructs requests based on selected service and operation.
Troubleshooting
- Invalid or missing API token: Ensure that the Zitadel API token credential is correctly configured and has sufficient permissions.
- Incorrect userId: When using
addOTPSMS, verify that theuserIdis valid and corresponds to an existing user in Zitadel. - JSON parsing errors: Input parameters are parsed as JSON if possible; malformed JSON input may cause errors. Provide plain strings where appropriate.
- Unsupported operation: If an operation is not recognized under the selected service, the node returns an empty JSON object. Verify that the operation name matches one supported by the chosen service.
- Network issues: Connectivity problems to the Zitadel API endpoint can cause failures. Check network access and endpoint availability.
Links and References
- Zitadel Official Documentation
- Zitadel API Reference
- nice-grpc GitHub Repository (for gRPC client usage)