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
Overview
This node integrates with the Zitadel API, allowing users to interact with various Zitadel services programmatically. Specifically, the listPasskeys operation under the "Default" resource fetches a list of passkeys associated with a given user ID from the selected Zitadel service.
Common scenarios for this node include:
- Retrieving authentication credentials (passkeys) for a user in an identity management system.
- Managing user security keys within an organization.
- Automating audits or reports on user authentication methods.
For example, you might use this node to list all passkeys registered by a user in the UserService to verify their authentication setup or to synchronize passkey data with another system.
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 passkeys you want to list. Required when Service is UserService and Operation is listPasskeys. |
Output
The node outputs a JSON object containing the response from the Zitadel API for the requested operation. For listPasskeys, the output JSON includes the list of passkeys associated with the specified user ID.
The exact structure depends on the Zitadel API response but typically includes details such as passkey IDs, creation dates, and metadata related to each passkey.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token (Personal Access Token) 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
- Missing or invalid API token: Ensure that the Zitadel API token credential is correctly configured and has sufficient permissions.
- Invalid userId: If the userId parameter is incorrect or does not exist, the API may return an error or empty results.
- Unsupported service-operation combination: The node only supports operations defined in the selected service; selecting an unsupported operation will result in no data returned.
- JSON parsing errors: Input parameters that expect JSON strings must be valid JSON; otherwise, the node falls back to treating them as plain strings.