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 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 wants to revoke or unregister a security key 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 as part of user lifecycle management.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to use. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, "UserService" must be selected. |
| 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 API authentication token credential for Zitadel (referred generically as an API key credential).
- The node uses the Zitadel gRPC client libraries bundled within the source code.
- The base URL for the Zitadel API is fixed as
https://zitadel.studentcouncil.dk. - No additional environment variables are explicitly required beyond the API credential.
Troubleshooting
- Invalid Credentials: If the API token is missing or invalid, the node will fail to authenticate. Ensure the correct API key credential is configured.
- Incorrect Service or Operation: Selecting a service other than "UserService" or an unsupported operation will result in no action or errors.
- Malformed Input: The
userIdandu2fIdmust be valid strings corresponding to existing entities in Zitadel. Invalid IDs will cause the API to return errors. - JSON Parsing Errors: The node attempts to parse input parameters as JSON if possible; malformed JSON inputs may cause failures. Provide plain strings for these fields.
- Network Issues: Connectivity problems to the Zitadel endpoint (
https://zitadel.studentcouncil.dk) will prevent execution.