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 provides an interface to interact with the Zitadel API, a platform for identity and access management. It supports multiple services such as UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, and UserSchemaService. The specific operation removeOTPSMS under the UserService resource allows removing or disabling the OTP (One-Time Password) SMS method for a user, which is useful in scenarios where you want to revoke SMS-based two-factor authentication for security or user preference reasons.
Practical examples:
- An administrator wants to disable SMS OTP for a user who lost their phone.
- Automating user security settings by removing SMS OTP when switching to app-based authenticators.
- Managing multi-factor authentication methods programmatically within workflows.
Properties
| Name | Meaning |
|---|---|
| Service | Selects the Zitadel service to use. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. Default is UserService. |
| userId | The unique identifier of the user whose OTP SMS method should be removed. Required when Service is UserService and Operation is removeOTPSMS. |
Output
The output JSON contains the response from the Zitadel API call corresponding to the invoked operation. For removeOTPSMS, it will typically include confirmation details about the removal of the OTP SMS method for the specified user. The exact structure depends on the Zitadel API response but generally includes status or updated user information.
No binary data output is indicated.
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 in n8n and has sufficient permissions.
- Incorrect userId: Verify that the userId parameter corresponds to an existing user in Zitadel.
- Operation not found: Confirm that the selected Service and Operation are compatible;
removeOTPSMSonly applies toUserService. - JSON parsing errors: Input parameters are parsed as JSON if possible; ensure string inputs are valid JSON or plain strings as expected.
- Network issues: Check connectivity to the Zitadel API endpoint.