Zitadel icon

Zitadel

Interact with the Zitadel API

verifyTOTPRegistration

AI-generated

Overview

This node interacts with the Zitadel API, a platform for identity and access management. Specifically, the verifyTOTPRegistration operation under the "Default" resource allows verifying a user's Time-based One-Time Password (TOTP) registration. This is useful in scenarios where multi-factor authentication (MFA) is enforced, and you need to confirm that a user has correctly registered their TOTP device by validating the provided code.

Practical examples include:

  • Verifying a user's TOTP during login or setup flows.
  • Automating security checks in workflows that require strong user authentication.
  • Integrating with custom user management systems to validate MFA status.

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 verification results such as success status or error details related to the TOTP verification process.

No binary data output is produced by this node.

Example output structure (simplified):

{
  "verified": true,
  "message": "TOTP registration verified successfully"
}

(Note: Actual fields depend on Zitadel API response.)

Dependencies

  • Requires an API authentication token (Personal Access Token) for Zitadel, configured in n8n 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 expired TOTP code: If the provided code is incorrect or expired, the API will reject verification. Ensure the user provides a current TOTP code.
  • Incorrect userId: Verification will fail if the user ID does not exist or is mistyped.
  • Authentication errors: Missing or invalid API tokens will cause authorization failures. Verify that the API key credential is correctly set up.
  • JSON parsing errors: Input parameters are parsed as JSON if possible; malformed JSON input may cause errors. Provide plain strings for simple fields like userId and code.

Links and References

Discussion