Actions42
- addHumanUser
- getUserByID
- 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
removePasskey
AI-generatedOverview
This node integrates with the Zitadel API, allowing users to perform various operations on different Zitadel services. Specifically, for the removePasskey operation under the UserService resource, it removes a passkey associated with a user account. This is useful in scenarios where an administrator or system needs to revoke a user's passkey-based authentication method, such as when a device is lost or compromised.
Practical examples:
- Removing a specific passkey from a user's account to enforce security policies.
- Managing user authentication methods programmatically within automated workflows.
- Cleaning up unused or outdated passkeys during user account maintenance.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. 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 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 generally includes confirmation of the removal or error details if the operation failed.
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: Ensure that the API key credential is correctly configured and has sufficient permissions.
- Incorrect
userIdorpasskeyId: Verify that the IDs correspond to existing entities in Zitadel. - Network connectivity problems: Confirm that the node can reach the Zitadel API endpoint.
Error messages:
- Authorization errors typically indicate invalid or expired tokens; refresh or update credentials.
- Not found errors suggest the specified user or passkey does not exist; double-check input values.
- Parsing errors may occur if input parameters are malformed JSON; ensure inputs are valid strings or JSON objects as expected.