Actions42
- listUsers
- registerTOTP
- addHumanUser
- getUserByID
- setEmail
- resendEmailCode
- verifyEmail
- setPhone
- removePhone
- resendPhoneCode
- verifyPhone
- updateHumanUser
- deactivateUser
- reactivateUser
- lockUser
- unlockUser
- deleteUser
- registerPasskey
- verifyPasskeyRegistration
- createPasskeyRegistrationLink
- listPasskeys
- removePasskey
- registerU2F
- verifyU2FRegistration
- removeU2F
- 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 verifyTOTPRegistration operation under the UserService resource, it verifies a user's Time-based One-Time Password (TOTP) registration by submitting a user ID and a verification code.
Common scenarios where this node is beneficial include:
- Automating multi-factor authentication setup verification in user management workflows.
- Integrating TOTP verification into custom identity or access management processes.
- Validating user-provided TOTP codes during onboarding or security checks.
Practical example:
- A workflow that triggers when a new user registers, then uses this node to verify their TOTP registration by providing their user ID and the TOTP code they generated.
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 TOTP registration is being verified. Required when Service is UserService and Operation is verifyTOTPRegistration. |
| code | The TOTP verification code provided by the user. Required when Service is UserService and Operation is verifyTOTPRegistration. |
Output
The node outputs a JSON object containing the response from the Zitadel API for the invoked operation. For verifyTOTPRegistration, this typically includes confirmation of whether the TOTP code was successfully verified or details about any errors.
No binary data output is produced by this node.
Example output structure (simplified):
{
"verified": true,
"message": "TOTP registration verified successfully."
}
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 the Zitadel API token is correctly set in the node credentials; otherwise, authorization will fail.
- Incorrect userId or code: Verify that the
userIdandcodeinputs are correct and correspond to a valid user and TOTP code. - JSON parsing errors: Input properties are parsed as JSON if possible; ensure string inputs like
userIdandcodeare valid strings and not malformed JSON. - Operation not found: If an unsupported operation is selected, the node returns empty JSON output. Confirm the operation name matches one supported by the selected service.