Actions42
- getUserByID
- addHumanUser
- listUsers
- setEmail
- resendEmailCode
- verifyEmail
- setPhone
- removePhone
- resendPhoneCode
- verifyPhone
- updateHumanUser
- deactivateUser
- reactivateUser
- lockUser
- unlockUser
- deleteUser
- registerPasskey
- verifyPasskeyRegistration
- createPasskeyRegistrationLink
- listPasskeys
- removePasskey
- registerU2F
- verifyU2FRegistration
- removeU2F
- registerTOTP
- verifyTOTPRegistration
- removeTOTP
- addOTPSMS
- removeOTPSMS
- addOTPEmail
- removeOTPEmail
- startIdentityProviderIntent
- retrieveIdentityProviderIntent
- addIDPLink
- listIDPLinks
- removeIDPLink
- passwordReset
- setPassword
- listAuthenticationMethodTypes
- createInviteCode
- resendInviteCode
- verifyInviteCode
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 wants to revoke a previously registered security key or passkey used for authentication.
Practical examples include:
- An administrator removing a compromised or lost hardware security key from a user's account.
- Automating cleanup of passkeys when deactivating user accounts.
- Managing user authentication methods programmatically within workflows.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to use. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. Default is UserService. |
| userId | The unique identifier of the user whose passkey is to be removed. Required for removePasskey operation under UserService. |
| passkeyId | The unique identifier of the passkey to remove from the specified user. Required for removePasskey operation under UserService. |
Output
The output JSON contains the response from the Zitadel API after attempting to remove the passkey. It reflects the result of the operation, which may include success confirmation or error details depending on the API response.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token (Personal Access Token) for Zitadel, provided via node 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 API token will cause authorization failures.
- Incorrect
userIdorpasskeyIdvalues will result in errors indicating that the resource was not found. - Network connectivity problems can prevent communication with the Zitadel API endpoint.
Error messages:
- Authorization errors typically indicate invalid or expired tokens; ensure the API key credential is valid.
- Not found errors suggest the specified user or passkey does not exist; verify IDs are correct.
- Parsing errors may occur if input parameters are malformed JSON; ensure string inputs are properly formatted.