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
registerPasskey
AI-generatedOverview
This node integrates with the Zitadel API, allowing users to perform various operations across multiple Zitadel services such as UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, and UserSchemaService. Specifically, the registerPasskey operation under the UserService resource enables registering a passkey for a user, which is typically part of implementing passwordless authentication or multi-factor authentication flows.
Common scenarios where this node is beneficial include:
- Automating user authentication setup by registering security keys (passkeys) programmatically.
- Managing user credentials and authentication methods within an organization's identity management system.
- Integrating Zitadel's identity platform capabilities into custom workflows in n8n.
Practical example:
- A workflow that registers a new passkey for a user after they complete a verification step, enhancing security by enabling hardware-backed authentication.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. Default is UserService. |
| userId | The unique identifier of the user for whom the passkey is being registered. Required for registerPasskey operation under UserService. |
| code | A code string required for the passkey registration process, likely representing a verification or challenge code. Required for registerPasskey. |
| authenticator | The authenticator identifier or data used during passkey registration. Required for registerPasskey. |
| domain | The domain context in which the passkey registration is taking place. Required for registerPasskey. |
Output
The node outputs a JSON object containing the response from the Zitadel API corresponding to the invoked operation. For the registerPasskey operation, this will typically include confirmation details about the passkey registration status or any relevant metadata returned by the API.
No binary data output is produced by this node.
Example output structure (simplified):
{
"json": {
// Response fields from Zitadel's registerPasskey API call
}
}
Dependencies
- Requires an API authentication token (Personal Access Token or similar) configured in n8n credentials to authorize requests to the Zitadel API.
- Connects to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk. - Uses gRPC client libraries internally to communicate with Zitadel services.
Troubleshooting
- Authentication errors: If the node fails due to authorization issues, verify that the API token credential is correctly set up and has sufficient permissions.
- Invalid input parameters: Ensure all required properties (
userId,code,authenticator,domain) are provided and correctly formatted. JSON parsing errors may occur if inputs are not valid JSON strings when expected. - Operation not found: Selecting an unsupported operation for the chosen service will result in no action; confirm that
registerPasskeyis selected underUserService. - Network issues: Connectivity problems to the Zitadel API endpoint can cause request failures; check network access and endpoint availability.