Zitadel icon

Zitadel

Interact with the Zitadel API

Overview

This node provides an interface to interact with the Zitadel API, a platform for identity and access management. Specifically, the removeU2F operation under the "Default" resource (mapped here as part of the UserService) allows users to remove a U2F (Universal 2nd Factor) device from a user's account. This is useful in scenarios where a user wants to revoke a registered security key or hardware token used for two-factor authentication.

Practical examples include:

  • An administrator removing a lost or compromised U2F device from a user's profile.
  • Automating cleanup of U2F devices when users leave an organization.
  • Managing multi-factor authentication devices programmatically via workflows.

Properties

Name Meaning
Service The Zitadel service to use. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, select UserService.
userId The unique identifier of the user from whom the U2F device will be removed.
u2fId The unique identifier of the U2F device to be removed from the specified user.

Output

The output JSON contains the response from the Zitadel API after attempting to remove the specified U2F device. It typically includes confirmation details or status information about the removal operation.

No binary data output is produced by this node.

Example output structure (simplified):

{
  "result": {
    // Details confirming the removal of the U2F device
  }
}

Dependencies

  • Requires an API authentication token (Personal Access Token) for Zitadel, provided via node credentials.
  • 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 gRPC client libraries.

Troubleshooting

  • Invalid or missing credentials: Ensure that a valid API token is configured in the node credentials; otherwise, authorization errors will occur.
  • Incorrect userId or u2fId: Providing invalid identifiers will result in errors from the Zitadel API indicating that the user or U2F device was not found.
  • Network issues: Connectivity problems to the Zitadel API endpoint can cause timeouts or connection errors.
  • JSON parsing errors: Input parameters are parsed as JSON if possible; malformed JSON strings in inputs may cause failures. Provide plain strings for simple IDs.

Links and References

Discussion