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
verifyPasskeyRegistration
AI-generatedOverview
This node integrates with the Zitadel API to perform various operations across multiple services such as UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, and UserSchemaService. Specifically, for the verifyPasskeyRegistration operation under the UserService resource, it verifies a user's passkey registration by sending the required data (user ID, passkey ID, public key credential, and passkey name) to the Zitadel backend.
Common scenarios where this node is beneficial include:
- Verifying new passkey registrations during user authentication setup.
- Managing user security credentials in identity and access management workflows.
- Automating user verification processes in custom authentication flows.
Practical example:
- When a user registers a new passkey on a web or mobile app, this node can be used to verify the registration details against Zitadel's service to ensure the passkey is valid and properly registered.
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 whose passkey registration is being verified. |
| passkeyId | The unique identifier of the passkey to verify. |
| publicKeyCredential | The public key credential string associated with the passkey registration. |
| passkeyName | A descriptive name for the passkey being registered. |
Output
The node outputs a JSON object containing the response from the Zitadel API for the invoked operation. For verifyPasskeyRegistration, the output JSON will contain the verification result details returned by the Zitadel UserService.
If the operation returns binary data (not applicable here), it would be included accordingly, but this operation deals with JSON responses only.
Example output structure (simplified):
{
"verificationResult": {
"success": true,
"message": "Passkey registration verified successfully"
}
}
Dependencies
- Requires an API authentication token (Personal Access Token or similar) for Zitadel, configured in n8n credentials.
- Depends on the Zitadel gRPC client libraries bundled within the node.
- Network access to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk.
Troubleshooting
- Invalid or missing credentials: Ensure that the API token is correctly set up in n8n credentials; otherwise, authorization errors will occur.
- Malformed input parameters: The node expects certain fields like
userId,passkeyId,publicKeyCredential, andpasskeyNameto be provided and correctly formatted. Missing or incorrect values may cause the API call to fail. - JSON parsing errors: Input parameters are parsed as JSON if possible. If the input strings are not valid JSON, the node falls back to using them as plain strings. Make sure inputs are correctly formatted.
- Operation not supported: If an unsupported operation is selected, the node returns an empty JSON object.
- Network issues: Connectivity problems to the Zitadel API endpoint will cause request failures.