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
Overview
This node provides an interface to interact with the Zitadel API, a platform for identity and access management. Specifically, the registerU2F operation under the "Default" resource (mapped here as part of the "UserService") allows registering a U2F (Universal 2nd Factor) device for a user. This is useful in scenarios where enhanced security via two-factor authentication is required.
Typical use cases include:
- Enabling users to register hardware security keys for multi-factor authentication.
- Automating user security setup workflows within an organization.
- Integrating Zitadel's identity services into custom automation pipelines.
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 for whom the U2F device will be registered. |
| domain | The domain context under which the U2F registration is performed. |
Output
The node outputs a JSON object representing the response from the Zitadel API for the registerU2F operation. This typically includes details about the U2F registration process, such as challenge data or confirmation of successful registration.
No binary data output is produced by this node.
Example output structure (simplified):
{
"challenge": "...",
"appId": "...",
"version": "...",
"keyHandle": "..."
}
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
- Invalid Credentials: If the API token is missing or invalid, the node will fail to authenticate. Ensure that a valid API key credential is configured.
- Incorrect Parameters: Missing or malformed
userIdordomainparameters can cause errors. Verify these inputs are correctly set. - Operation Not Found: Selecting an unsupported operation for the chosen service will result in no action. Confirm that
registerU2Fis selected underUserService. - JSON Parsing Errors: Input parameters are parsed as JSON if possible; invalid JSON strings will fallback to raw string usage. Ensure input formats are correct.