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
resendEmailCode
AI-generatedOverview
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. Default is UserService. |
| 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 code expected to be returned or used in the resend process (likely for validation). |
Output
The node outputs a JSON object containing the response from the Zitadel API corresponding to 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 produced by this node.
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 the API key credential is correctly set up and has sufficient permissions.
- Incorrect userId: Verify that the user ID exists in the Zitadel system; otherwise, the resend will fail.
- Malformed input parameters: The node attempts to parse JSON inputs; ensure that string inputs are valid JSON if applicable.
- Operation not supported: If the selected operation does not exist in the chosen service, the node returns empty JSON without error—verify correct operation name.
- Network issues: Confirm network connectivity to the Zitadel API endpoint.