Actions42
- getUserByID
- addHumanUser
- 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 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 newly registered passkeys for users in an authentication system.
- Automating user security workflows that involve passkey management.
- Integrating Zitadel's identity and access management features into custom automation pipelines.
Practical example:
- After a user registers a new passkey on a website, this node can be used to verify the registration by providing the necessary passkey details, ensuring the passkey is valid and securely stored.
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 verified. |
Output
The node outputs a JSON object containing the response from the Zitadel API for the invoked operation. For verifyPasskeyRegistration, this typically includes verification results or status information related to the passkey registration.
If the node supports binary data output (not indicated here), it would represent binary content returned by the API, but this operation deals with JSON responses only.
Dependencies
- Requires an API authentication token (Personal Access Token or similar) 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 or missing credentials: Ensure the API token is correctly configured in the node credentials; otherwise, authorization errors will occur.
- Malformed input parameters: The node attempts to parse JSON strings for inputs; invalid JSON or incorrect parameter formats may cause errors. Verify that all required fields (
userId,passkeyId,publicKeyCredential,passkeyName) are correctly set. - Operation not found: If an unsupported operation is selected, the node returns an empty JSON object. Confirm the operation name matches one supported by the selected service.
- Network issues: Connectivity problems to the Zitadel API endpoint will result in request failures. Check network access and endpoint availability.