Zitadel

Overview

This node integrates with the Zitadel API to perform various operations across multiple services such as UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, and UserSchemaService. Specifically, for the verifyPasskeyRegistration operation under the UserService resource, it verifies a user's passkey registration by sending the required user ID, passkey ID, public key credential, and passkey name to the Zitadel API.

Common scenarios where this node is beneficial include:

• Verifying newly registered passkeys for users in an authentication system.
• Integrating passkey-based multi-factor authentication verification into workflows.
• Automating user security checks during onboarding or access management processes.

Practical example:

• After a user registers a new passkey on a website, this node can be used to verify the registration by providing the user’s ID, the passkey ID, the public key credential data, and a name for the passkey.

Properties

Output

The node outputs a JSON object containing the response from the Zitadel API for the invoked operation. For verifyPasskeyRegistration, this will typically include details about the verification result of the passkey registration, such as success status or error information.

If the operation involves binary data (not applicable here), the node would output that accordingly, but for this operation, only JSON output is expected.

Example output structure (simplified):

{
  "verificationResult": {
    "success": true,
    "message": "Passkey registration verified successfully."
  }
}

Dependencies

• Requires an API authentication token (Personal Access Token) for Zitadel, 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 credentials: Ensure that a valid API authentication token is provided in the node credentials; otherwise, authorization errors will occur.
• Malformed input parameters: The node attempts to parse JSON inputs; if the publicKeyCredential or other fields are not correctly formatted, parsing errors may arise. Provide valid JSON strings or plain strings as required.
• Operation not found: If an unsupported operation is selected, the node returns empty JSON output. Verify that the operation name matches one supported by the selected service.
• Network issues: Connectivity problems to the Zitadel API endpoint will cause request failures. Check network access and endpoint availability.

Links and References

• Zitadel Official Documentation
• WebAuthn / Passkey Concepts
• n8n Documentation - Creating Custom Nodes