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
addOTPEmail
AI-generatedOverview
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 addOTPEmail operation under the "Default" resource enables adding a One-Time Password (OTP) email for a user by specifying their user ID.
Common scenarios where this node is beneficial include automating user management tasks, enhancing authentication flows by adding OTP emails, managing organizational data, or triggering custom actions within Zitadel. For example, an administrator could use this node to programmatically add OTP email addresses to users for multi-factor authentication setup.
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 to whom the OTP email will be added. Required when Service is UserService and Operation is addOTPEmail. |
Output
The node outputs a JSON object representing the response from the Zitadel API for the invoked operation. This typically includes details about the result of the addOTPEmail action, such as confirmation of the OTP email addition 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 internally 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 service or operation selection: Selecting a service-operation combination not supported by the node will result in empty or error responses.
- Malformed input parameters: Input fields like
userIdmust be valid strings; invalid JSON or incorrect types may cause parsing errors. - Network issues: Connectivity problems to the Zitadel API endpoint can cause timeouts or failures.