Actions42
- getUserByID
- addHumanUser
- 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, the resendEmailCode operation under the "Default" resource (mapped to the UserService) enables resending an email verification or confirmation code to a user identified by their user ID.
Common scenarios for this node include:
- Resending verification codes when users fail to receive or lose their original email code.
- Triggering email-based authentication flows in user management systems.
- Automating user onboarding processes that require email confirmation.
For example, if a user requests a new verification email after signing up, this node can be used to resend the email code 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 email code will be resent. Required for resendEmailCode operation under UserService. |
| sendCode | A string parameter required by the resendEmailCode operation; likely represents the code or flag to trigger sending the email code. |
| returnCode | A string parameter required by the resendEmailCode operation; possibly controls whether the code should be returned or some related behavior. |
Output
The node outputs a JSON object containing the response from the Zitadel API corresponding to the invoked operation. For the resendEmailCode operation, the output JSON will typically include details about the success or failure of the resend request, such as status messages or confirmation flags.
No binary data output is indicated in the source code.
Example output structure (simplified):
{
"status": "success",
"message": "Email code resent successfully",
"userId": "example-user-id"
}
Dependencies
- Requires an API key credential for authenticating with the Zitadel API.
- Uses the Zitadel gRPC client libraries bundled within the node.
- The node expects a personal access token (PAT) credential configured in n8n for authorization.
- Network access to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk.
Troubleshooting
- Invalid or missing credentials: If the API key or token is not set or expired, the node will fail to authenticate. Ensure the correct API key credential is configured.
- Incorrect parameters: Missing or malformed
userId,sendCode, orreturnCodeparameters may cause the API call to fail. Verify all required fields are correctly provided. - API errors: Errors returned from the Zitadel API (e.g., user not found, rate limits) will be included in the output JSON. Review these messages to adjust inputs or retry later.
- JSON parsing issues: The node attempts to parse input parameters as JSON; invalid JSON strings will fallback to raw strings. Ensure complex parameters are properly formatted.