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, a platform for identity and access management. Specifically, the setEmail operation under the default resource (which corresponds to the "UserService" service) allows updating or setting a user's email address along with related verification parameters.
Typical use cases include:
- Updating a user's email in an identity management system.
- Triggering email verification workflows by sending verification codes.
- Managing user email verification status programmatically.
For example, you might use this node to update a user's email after they submit a change request on your application, optionally sending a verification code to confirm ownership of the new email.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For setEmail, must be UserService. |
| userId | The unique identifier of the user whose email is being set or updated. |
| The new email address to assign to the user. | |
| sendCode | A string indicating whether to send a verification code to the new email. |
| returnCode | A string indicating whether to return the verification code in the response. |
| isVerified | A string indicating whether the email should be marked as verified immediately. |
Output
The node outputs a JSON object representing the response from the Zitadel API's setEmail method. This typically includes details about the updated user email state, any verification codes sent or returned, and confirmation of the operation's success.
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 Credentials: If the API token is missing or invalid, the node will fail to authenticate. Ensure the correct API key/token is configured in n8n credentials.
- Missing Required Parameters: The
userId,email,sendCode,returnCode, andisVerifiedfields are required. Omitting them will cause errors. - JSON Parsing Errors: Input parameters are parsed as JSON if possible. Malformed JSON strings in inputs may cause parsing failures.
- Operation Not Supported: Using the
setEmailoperation with a service other thanUserServicewill result in no action or errors. - Network Issues: Connectivity problems to the Zitadel API endpoint will cause request failures.