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, for the registerTOTP operation under the "Default" resource, it facilitates registering a Time-based One-Time Password (TOTP) for a user. This is useful in scenarios where multi-factor authentication (MFA) setup is required, enhancing account security by enabling TOTP-based verification.
Practical examples include:
- Automating the enrollment of users into MFA workflows.
- Integrating TOTP registration as part of user onboarding processes.
- Managing user authentication settings programmatically within an organization.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, typically "UserService". |
| userId | The unique identifier of the user for whom the TOTP registration is being performed. Required when Service is "UserService" and Operation is "registerTOTP". |
Output
The node outputs a JSON object representing the response from the Zitadel API for the invoked operation. For registerTOTP, this will typically include details about the TOTP registration status or any relevant metadata returned by the API.
No binary data output is indicated by the source code.
Example output structure (simplified):
{
"json": {
// Response fields from Zitadel's registerTOTP method
}
}
Dependencies
- Requires an API authentication token credential for Zitadel (referred generically as an API key credential).
- Connects to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk. - Uses gRPC client libraries (
nice-grpc) to communicate with Zitadel services. - The node dynamically selects the appropriate Zitadel service and method based on input parameters.
Troubleshooting
Common issues:
- Missing or invalid API authentication token will cause authorization failures.
- Providing incorrect or missing
userIdwhen required will result in errors from the API. - Malformed JSON input for request parameters may cause parsing errors.
Error messages:
- Authorization errors typically indicate problems with the provided API token; ensure the token is valid and has necessary permissions.
- Validation errors from Zitadel API usually point to missing or invalid input parameters; verify that all required fields are correctly set.
- JSON parsing errors occur if input parameters expected as JSON strings are malformed; ensure proper JSON formatting.