Zitadel

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 Default resource (mapped here as the UserService), it verifies a user's Time-based One-Time Password (TOTP) registration by submitting a user ID and a verification code.

Common scenarios include:

• Verifying a user's TOTP setup during multi-factor authentication enrollment.
• Confirming that a user has correctly registered their authenticator app or device.
• Automating security workflows where TOTP verification is required before granting access or completing sensitive actions.

Practical example:

• A workflow that triggers when a new user registers, then calls this node to verify their TOTP registration using the provided code from their authenticator app.

Properties

Output

The node outputs a JSON object containing the response from the Zitadel API's verifyTOTPRegistration method. This response typically includes confirmation of whether the TOTP registration was successfully verified or details about any errors encountered.

No binary data output is produced by this operation.

Example output structure (simplified):

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

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 code: If the TOTP code is incorrect or expired, the API will reject the verification. Ensure the user provides a current code from their authenticator app.
• Incorrect userId: Verification will fail if the user ID does not correspond to a valid user with a pending TOTP registration.
• Authentication errors: Missing or invalid API tokens will cause authorization failures. Verify that the API key credential is correctly set up in n8n.
• Network issues: Connectivity problems to the Zitadel API endpoint can cause timeouts or connection errors.
• JSON parsing errors: Input properties 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

• Zitadel Official Documentation
• TOTP Multi-Factor Authentication Concepts
• n8n Documentation on Creating Custom Nodes