ZitadelInstall

Overview

This node integrates with the Zitadel API, allowing users to interact with various Zitadel services programmatically. Specifically, the listPasskeys operation under the "Default" resource fetches a list of passkeys associated with a given user ID from the selected Zitadel service.

Common scenarios for this node include:

• Retrieving authentication credentials (passkeys) for a user in an identity management system.
• Managing user security keys within an organization.
• Automating audits or synchronization of user authentication methods.

For example, an administrator could use this node to list all passkeys registered by a user to verify their authentication methods or to migrate them to another system.

Properties

Output

The output JSON contains the raw response from the Zitadel API corresponding to the listPasskeys request. This typically includes details about the user's passkeys such as key IDs, creation dates, and metadata related to each passkey.

No binary data output is produced by this node.

Example output structure (simplified):

{
  "passkeys": [
    {
      "id": "string",
      "createdAt": "timestamp",
      "displayName": "string",
      "publicKey": "string",
      ...
    }
  ],
  "totalCount": number,
  ...
}

Dependencies

• Requires an API authentication token credential for Zitadel (referred generically as an API key credential).
• The node uses gRPC clients generated for Zitadel services.
• Endpoint URL is fixed to https://zitadel.studentcouncil.dk.
• No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

• Invalid or missing API token: Ensure that the API key credential is correctly configured and has sufficient permissions to call the requested service and operation.
• Incorrect userId: The userId must be valid and exist in the Zitadel system; otherwise, the API may return errors or empty results.
• Unsupported operation for selected service: Selecting an operation not supported by the chosen service will result in no action or empty output.
• JSON parsing errors on input properties: Input parameters like query or queries (if used) expect valid JSON strings; malformed JSON will cause errors.
• Network or endpoint issues: Verify connectivity to the Zitadel endpoint and that the URL has not changed.

Links and References

• Zitadel Official Documentation
• Zitadel API Reference
• n8n Documentation on Creating Custom Nodes