Actions42
- listUsers
- registerTOTP
- addHumanUser
- getUserByID
- setEmail
- resendEmailCode
- verifyEmail
- setPhone
- removePhone
- resendPhoneCode
- verifyPhone
- updateHumanUser
- deactivateUser
- reactivateUser
- lockUser
- unlockUser
- deleteUser
- registerPasskey
- verifyPasskeyRegistration
- createPasskeyRegistrationLink
- listPasskeys
- removePasskey
- registerU2F
- verifyU2FRegistration
- removeU2F
- 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 removeU2F operation under the "Default" resource allows removing a U2F (Universal 2nd Factor) device from a user account. This is useful in scenarios where a userβs security key or hardware token needs to be deregistered, such as when a device is lost, replaced, or compromised.
Practical examples include:
- An administrator removing a registered U2F device from a user's profile.
- Automating cleanup of old or inactive U2F devices linked to users.
- Managing multi-factor authentication devices programmatically within 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 remove from the specified user. |
Output
The output JSON contains the response from the Zitadel API after attempting to remove the 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:
{
// Response fields depend on Zitadel's UserService removeU2F method,
// usually including success status or error details.
}
Dependencies
- Requires an active connection to the Zitadel API endpoint (
https://zitadel.studentcouncil.dk). - Needs an API authentication token (Personal Access Token) configured in the node credentials to authorize requests.
- Uses gRPC client libraries internally to communicate with Zitadel services.
Troubleshooting
- Invalid Credentials: If the API token is missing or invalid, the node will fail to authenticate. Ensure the API key credential is correctly set up.
- Incorrect userId or u2fId: Providing wrong identifiers will cause the API to return errors indicating that the user or U2F device was not found.
- Network Issues: Connectivity problems to the Zitadel endpoint can cause timeouts or failures.
- JSON Parsing Errors: Input parameters are parsed as JSON if possible; malformed JSON strings may cause errors. Provide plain strings for simple IDs.
Links and References
This summary is based solely on static analysis of the provided source code and property definitions.