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
listPasskeys
AI-generatedOverview
This node integrates with the Zitadel API, allowing users to interact with various Zitadel services programmatically. Specifically, the listPasskeys operation under the "Default" resource (mapped here as a service-operation pair) 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.
- Auditing or synchronizing user authentication methods across systems.
For example, you might use this node to list all passkeys registered by a user in the UserService to verify their authentication methods or to display them in an admin dashboard.
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 will include the list of passkeys associated with the specified user ID, structured according to Zitadel's API response schema for that method.
No binary data output is produced by this node.
Example output structure (simplified):
{
"passkeys": [
{
"id": "string",
"name": "string",
"createdAt": "timestamp",
...
},
...
]
}
Dependencies
- Requires an API authentication token credential for Zitadel (referred generically as an API key credential).
- Uses the Zitadel gRPC client libraries bundled within the node.
- The node connects to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk. - No additional environment variables are explicitly required beyond the API credential.
Troubleshooting
- Invalid or missing API token: If the node fails to authenticate, ensure the API key credential is correctly configured and has sufficient permissions.
- Incorrect userId: Providing an invalid or non-existent userId will result in empty or error responses. Verify the userId before running the node.
- Unsupported service-operation combination: Selecting an operation not supported by the chosen service will cause the node to return an empty JSON object.
- JSON parsing errors: Input parameters like query strings must be valid JSON if expected; otherwise, the node falls back to string values.