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
registerU2F
AI-generatedOverview
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 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:
- Adding a hardware security key (like YubiKey) to a user's account.
- Enabling multi-factor authentication workflows in custom automation.
- Managing user authentication methods programmatically within n8n workflows.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to use. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, "UserService" is relevant. |
| 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's registerU2F method. This typically includes details about the U2F registration process or confirmation of successful registration.
No binary data output is produced by this node.
Example output structure (simplified):
{
"challenge": "...",
"appId": "...",
"version": "...",
"keyHandle": "..."
}
(Note: Actual fields depend on Zitadel's API response for U2F registration.)
Dependencies
- Requires an API authentication token credential for Zitadel (referred generically as an API key credential).
- Uses the Zitadel gRPC client libraries bundled within the node.
- The node connects to the Zitadel API endpoint at
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 API key credential is correctly configured.
- Incorrect Parameters: Providing an invalid
userIdordomainmay cause the API to reject the request. Verify these values before execution. - JSON Parsing Errors: Input parameters are parsed as JSON if possible; malformed JSON strings will cause errors. Provide valid JSON or plain strings accordingly.
- Operation Not Found: If the selected operation does not exist in the chosen service, the node returns an empty JSON object. Confirm that
registerU2Fis selected under theUserService.