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, allowing users to interact with various Zitadel services programmatically. Specifically, the registerTOTP operation under the "Default" resource enables registering a Time-based One-Time Password (TOTP) for a user, which is commonly used to set up two-factor authentication (2FA). This enhances account security by requiring a second verification step during login.
Typical use cases include:
- Automating the setup of 2FA for new or existing users.
- Integrating secure authentication flows in custom workflows.
- Managing user security settings within an organization.
For example, an admin could trigger this node to register TOTP for a user immediately after their account creation, ensuring they have 2FA enabled from the start.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For registerTOTP, select UserService. |
| userId | The unique identifier of the user for whom the TOTP registration will be performed. Required when Service is UserService and Operation is registerTOTP. |
Output
The node outputs a JSON object containing the response from the Zitadel API corresponding to the registerTOTP operation. This typically includes details about the TOTP registration process, such as secret keys, QR codes, or status messages needed to complete the 2FA setup on the user's device.
No binary data output is indicated by the source code.
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
- Invalid or missing API token: Ensure that the API key credential is correctly configured and has sufficient permissions.
- Incorrect
userId: Verify that the user ID exists in Zitadel; otherwise, the API call will fail. - Unsupported operation or service: Confirm that the selected service and operation are valid and supported by Zitadel.
- JSON parsing errors: Input parameters are parsed as JSON if possible; malformed JSON strings can cause failures. Provide valid JSON or plain strings accordingly.
- Network issues: Check connectivity to the Zitadel API endpoint.
Common error messages will generally come from the Zitadel API and may indicate authorization failures, invalid parameters, or service unavailability.