ZitadelInstall

Overview

This node integrates with the Zitadel API, allowing users to perform various operations across multiple Zitadel services. Specifically, the registerPasskey operation under the "Default" resource (mapped here as part of the UserService) enables registering a passkey for a user. This is useful in scenarios where passwordless authentication or multi-factor authentication using passkeys is implemented.

Practical examples include:

• Registering a new passkey credential for a user to enable secure login without passwords.
• Automating user security setup workflows by programmatically adding authenticators.
• Integrating Zitadel's identity management features into custom automation pipelines.

Properties

Output

The node outputs a JSON object representing the response from the Zitadel API for the registerPasskey operation. This typically includes confirmation details about the registered passkey, status information, and any metadata returned by the API.

No binary data output is indicated or handled by this node.

Example output structure (simplified):

{
  "registeredPasskey": {
    "id": "string",
    "userId": "string",
    "authenticator": "string",
    "status": "string",
    "createdAt": "timestamp"
  }
}

Dependencies

• Requires an API key credential for Zitadel (referred generically as an API authentication token).
• The node uses gRPC clients generated from Zitadel's protobuf definitions to communicate with the Zitadel API endpoint at https://zitadel.studentcouncil.dk.
• No additional external dependencies beyond the bundled Zitadel client libraries and n8n's credential system.

Troubleshooting

• Common issues:

  • Invalid or missing API authentication token will cause authorization failures.
  • Incorrect or malformed input parameters (e.g., invalid userId or code) may result in API errors.
  • Network connectivity issues to the Zitadel endpoint can cause timeouts or connection errors.

• Error messages:

  • Authorization errors typically indicate missing or invalid credentials; ensure the API key/token is correctly configured.
  • Validation errors on input fields suggest checking the format and presence of required parameters like userId, code, authenticator, and domain.
  • Unexpected API responses might require verifying the Zitadel service availability or reviewing API version compatibility.

Links and References

• Zitadel Official Documentation
• Zitadel API Reference
• n8n Custom Node Development Guide