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 interact with various Zitadel services programmatically. Specifically, the resendEmailCode operation under the "Default" resource (mapped here as part of the UserService) enables resending an email verification or confirmation code to a user. This is useful in scenarios where a user did not receive the original email or the code expired.
Practical examples include:
- Resending a verification email during user registration.
- Triggering a resend of a password reset or multi-factor authentication code.
- Automating user onboarding flows that require email confirmation.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to use. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, "UserService" is relevant. |
| userId | The unique identifier of the user to whom the email code should be resent. |
| sendCode | The code or token that triggers sending the email code. |
| returnCode | A string parameter likely used to specify or capture the returned code from the resend action. |
Output
The output is a JSON object containing the response from the Zitadel API for the resendEmailCode operation. The exact structure depends on the Zitadel API's response but generally includes status information about the resend request.
No binary data output is indicated by the source code.
Dependencies
- Requires an API authentication token (Personal Access Token) configured in n8n credentials for Zitadel.
- Connects to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk. - Uses gRPC clients generated from Zitadel protobuf definitions to communicate with the API.
Troubleshooting
- Common issues:
- Invalid or missing API token will cause authorization failures.
- Incorrect
userIdmay result in errors indicating the user was not found. - Malformed JSON input for parameters could cause parsing errors.
- Error messages:
- Authorization errors typically mean the API key is invalid or expired; reconfigure credentials.
- Validation errors on parameters suggest checking the input values and types.
- Network or connectivity errors indicate issues reaching the Zitadel API endpoint.