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 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 as a second factor.
- Automating the registration process of U2F devices within an organization's identity management workflow.
- Integrating Zitadel's user security features 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 challenge or confirmation data returned by the API.
The output structure is:
{
// Response fields depend on Zitadel's UserService.registerU2F method
}
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token (Personal Access Token) for Zitadel, configured in n8n credentials.
- Connects to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk. - Uses gRPC client libraries internally to communicate with Zitadel services.
Troubleshooting
- Invalid or missing credentials: Ensure that the Zitadel API token is correctly set up in n8n credentials.
- Incorrect userId or domain: Verify that the
userIdanddomainparameters are valid and correspond to existing entities in Zitadel. - Operation not found: If the selected operation does not exist in the chosen service, the node returns an empty JSON object.
- JSON parsing errors: Input properties are parsed as JSON if possible; ensure string inputs are valid JSON or plain strings as expected.
- Network issues: Confirm network connectivity to the Zitadel API endpoint.