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 interacts with the Zitadel API, a platform for identity and access management. Specifically, the verifyTOTPRegistration operation under the "Default" resource (mapped to the UserService) verifies a user's Time-based One-Time Password (TOTP) registration by sending a user ID and a TOTP code to the Zitadel service.
Common scenarios where this node is useful include:
- Verifying a user's two-factor authentication setup during login or security checks.
- Automating security workflows that require confirmation of TOTP registration.
- Integrating Zitadel's authentication verification into custom automation pipelines.
For example, after a user registers their TOTP device, this node can be used to confirm the registration by verifying the provided TOTP code against Zitadel's backend.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to use. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, select UserService. |
| userId | The unique identifier of the user whose TOTP registration is being verified. |
| code | The TOTP code provided by the user to verify their registration. |
Output
The node outputs a JSON object containing the response from the Zitadel API's verifyTOTPRegistration method. This typically includes information about whether the TOTP verification was successful or not, along with any relevant metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential (Personal Access Token) for authenticating with the Zitadel API.
- The node uses gRPC clients generated from Zitadel's protobuf definitions to communicate with the API endpoint at
https://zitadel.studentcouncil.dk. - Proper configuration of the Zitadel API credentials in n8n is necessary for successful execution.
Troubleshooting
- Invalid or missing API token: If the Personal Access Token is invalid or missing, the node will fail to authenticate. Ensure the API key credential is correctly set up.
- Incorrect userId or code: Providing an incorrect user ID or TOTP code will result in verification failure. Double-check these inputs.
- Network issues: Connectivity problems to the Zitadel API endpoint may cause timeouts or errors.
- JSON parsing errors: Input properties are parsed as JSON if possible; malformed JSON strings in inputs could cause errors. Provide plain strings for simple fields like
userIdandcode.