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
registerTOTP
AI-generatedOverview
This node integrates with the Zitadel API, allowing users to perform various operations across multiple Zitadel services. Specifically, for the registerTOTP operation under the "Default" resource, it enables registering a Time-based One-Time Password (TOTP) for a user. This is useful in scenarios where multi-factor authentication (MFA) setup is required to enhance account security.
Practical examples include:
- Registering TOTP for a user after they enable MFA in an application.
- Automating security setups for new users by programmatically configuring their TOTP.
- Integrating with identity management workflows that require secure user verification.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, "UserService" is relevant. |
| 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 representing the response from the Zitadel API for the registerTOTP operation. This typically includes details about the TOTP registration status or any relevant metadata returned by the API.
No binary data output is involved in this operation.
Example output structure (simplified):
{
"json": {
// Response fields from Zitadel's registerTOTP API call
}
}
Dependencies
- Requires an API key credential for authenticating with the Zitadel API.
- The node uses gRPC clients generated from Zitadel's protobuf definitions to communicate with the API endpoint at
https://zitadel.studentcouncil.dk. - Proper configuration of the Zitadel API credentials within n8n is necessary.
Troubleshooting
Common issues:
- Missing or invalid API credentials can cause authentication failures.
- Providing an incorrect or non-existent
userIdmay result in errors or empty responses. - Network connectivity issues to the Zitadel API endpoint can prevent successful execution.
Error messages:
- Authorization errors indicating missing or invalid tokens: Ensure the API key credential is correctly set up.
- Validation errors related to input parameters: Verify that
userIdis provided and correctly formatted. - Unexpected API errors: Check Zitadel service status and network connectivity.