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 on different Zitadel services. Specifically, for the setEmail operation under the default resource, it updates or sets a user's email address within the UserService. This is useful in scenarios where you need to programmatically manage user contact information, such as updating user profiles, verifying emails, or triggering email-related workflows.
Practical examples include:
- Updating a user's email after they submit a change request.
- Sending verification codes to new email addresses.
- Marking an email as verified after confirmation.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, use 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 (e.g., "true" or "false"). |
| returnCode | A string specifying if the verification code should be returned in the response. |
| isVerified | A string indicating whether the email should be marked as verified immediately (e.g., "true" or "false"). |
Output
The node outputs a JSON object representing the response from the Zitadel UserService's setEmail method. This typically includes details about the email update operation, such as success status, any verification codes sent or returned, and possibly updated user metadata.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"email": "user@example.com",
"isVerified": true,
"verificationCodeSent": true,
"returnedCode": "123456"
}
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 bundled with the node for communication.
Troubleshooting
- Invalid or missing API token: Ensure that the Zitadel API key credential is correctly configured and has sufficient permissions.
- Incorrect userId or email format: Validate that the
userIdexists and theemailis properly formatted. - JSON parsing errors: Input properties are parsed as JSON if possible; ensure strings like
sendCode,returnCode, andisVerifiedare valid JSON or simple strings. - Operation not found: Confirm that the selected service is
UserServiceand operation issetEmail. - Network issues: Verify connectivity to the Zitadel API endpoint.