ZitadelInstall

Overview

This node provides an interface to interact with the Zitadel API, a platform for identity and access management. Specifically, the removePasskey operation under the UserService resource allows users to remove a passkey associated with a user account. This is useful in scenarios where a user’s security credentials need to be revoked or updated, such as when a device is lost or compromised.

Practical examples include:

• Removing a registered hardware security key (passkey) from a user's account.
• Managing user authentication methods programmatically within automated workflows.
• Enhancing security by revoking outdated or unused passkeys.

Properties

Output

The node outputs a JSON object representing the response from the Zitadel API after attempting to remove the passkey. The exact structure depends on the API's response but typically includes confirmation of the removal or error details if the operation failed.

No binary data output is produced by this operation.

Example output JSON structure (simplified):

{
  "result": "success",
  "removedPasskeyId": "string"
}

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

• Common issues:

  • Invalid or missing userId or passkeyId parameters will cause the operation to fail.
  • Authentication errors if the API token is invalid or expired.
  • Network connectivity issues to the Zitadel API endpoint.

• Error messages and resolutions:

  • "Unauthorized" — Check that the API token credential is correctly set and has sufficient permissions.
  • "User not found" — Verify the userId is correct and exists in the Zitadel system.
  • "Passkey not found" — Confirm the passkeyId corresponds to a passkey registered to the specified user.
  • JSON parsing errors — Ensure input parameters are provided as plain strings; the node attempts to parse JSON but expects simple string inputs for these fields.

Links and References

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