Actions42
- listUsers
- registerTOTP
- addHumanUser
- getUserByID
- setEmail
- resendEmailCode
- verifyEmail
- setPhone
- removePhone
- resendPhoneCode
- verifyPhone
- updateHumanUser
- deactivateUser
- reactivateUser
- lockUser
- unlockUser
- deleteUser
- registerPasskey
- verifyPasskeyRegistration
- createPasskeyRegistrationLink
- listPasskeys
- removePasskey
- registerU2F
- verifyU2FRegistration
- removeU2F
- 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 perform various operations across multiple Zitadel services. Specifically, for the removeTOTP operation under the "Default" resource (which corresponds to the UserService), it removes a user's Time-based One-Time Password (TOTP) configuration. This is useful in scenarios where a user needs to reset or disable their two-factor authentication setup.
Practical examples include:
- An administrator disabling TOTP for a user who lost access to their authenticator app.
- Automating security resets during user account recovery processes.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For removeTOTP, must be UserService. |
| userId | The unique identifier of the user whose TOTP configuration will be removed. Required when Service is UserService and Operation is removeTOTP. |
Output
The node outputs a JSON object representing the response from the Zitadel API after attempting to remove the TOTP configuration. The exact structure depends on the Zitadel API's response schema for this operation but generally includes confirmation of success or details about any errors.
No binary data output is produced by this operation.
Example output JSON structure (simplified):
{
"result": "success",
"details": {
"userId": "string",
"totpRemoved": true
}
}
Dependencies
- Requires an API authentication token credential for Zitadel (referred generically as an API key credential).
- The node uses the Zitadel gRPC client libraries bundled within the node code.
- Network access to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk. - Proper configuration of the Zitadel API credentials in n8n.
Troubleshooting
Common issues:
- Missing or invalid API authentication token: Ensure the API key credential is correctly configured and has sufficient permissions.
- Incorrect
userId: Verify that the user ID exists in the Zitadel system. - Using the wrong Service option: For
removeTOTP, the Service must be set toUserService.
Error messages:
- Authorization errors typically indicate invalid or missing API credentials.
- Validation errors may occur if required parameters like
userIdare missing or malformed. - Network errors suggest connectivity issues to the Zitadel API endpoint.
Resolving these usually involves checking credentials, input parameters, and network connectivity.