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 perform various operations across multiple Zitadel services. Specifically, for the removeOTPEmail operation under the "Default" resource (which corresponds to the UserService), it removes the One-Time Password (OTP) email configuration for a specified user. This is useful in scenarios where an administrator or system needs to disable OTP email-based two-factor authentication for a user.
Practical examples include:
- Disabling OTP email for a user who no longer wants to use email-based 2FA.
- Resetting a user's multi-factor authentication settings as part of account recovery or security policy changes.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, select "UserService". |
| userId | The unique identifier of the user whose OTP email should be removed. Required when Service is "UserService" and Operation is "removeOTPEmail". |
Output
The output JSON contains the response from the Zitadel API corresponding to the removeOTPEmail operation. It typically includes confirmation details about the removal action or any relevant metadata returned by the API.
No binary data output is produced by this node.
Example output structure (simplified):
{
// Response fields depend on Zitadel's removeOTPEmail API response
}
Dependencies
- Requires an API authentication token (Personal Access Token) for Zitadel, configured in n8n 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 Zitadel API token credential is correctly set up and has sufficient permissions.
- Incorrect userId: Verify that the
userIdprovided exists and is valid within your Zitadel instance. - Operation not found: If the selected operation does not exist for the chosen service, the node will return an empty JSON object.
- JSON parsing errors: Input parameters are parsed as JSON if possible; ensure string inputs are valid JSON or plain strings as expected.
- Network issues: Confirm network connectivity to the Zitadel API endpoint.