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 such as UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, and UserSchemaService. Specifically, for the addOTPEmail operation under the Default resource, it enables adding a One-Time Password (OTP) email to a user account within the selected service.
Common scenarios include automating user authentication workflows, managing user credentials, or enhancing security by programmatically adding OTP emails for multi-factor authentication setups.
For example, an organization could use this node to add OTP email addresses to users in bulk, facilitating secure login processes without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. Default is UserService. |
| userId | The unique identifier of the user to whom the OTP email will be added. Required when Service is UserService and Operation is addOTPEmail. |
Output
The node outputs a JSON object representing the response from the Zitadel API for the invoked operation. This typically includes details about the success or failure of the addOTPEmail request, such as confirmation of the OTP email addition or error information.
No binary data output is produced by this node.
Example output structure:
{
"json": {
// Response fields from the Zitadel API for addOTPEmail operation
}
}
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
- Authentication errors: Ensure that the API token credential is valid and has sufficient permissions to perform the requested operation.
- Invalid userId: Verify that the
userIdprovided exists in the specified service context. - JSON parsing errors: Input parameters are parsed as JSON if applicable; ensure correct JSON formatting for complex inputs.
- Operation not found: Confirm that the selected operation is supported by the chosen service.
- Network issues: Check connectivity to the Zitadel API endpoint.