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
verifyInviteCode
AI-generatedOverview
This node integrates with the Zitadel API, allowing users to perform various operations across multiple Zitadel services. Specifically, for the verifyInviteCode operation under the default resource, it verifies a user's invite code by sending the user ID and verification code to the Zitadel UserService. This is useful in scenarios where you need to confirm that an invitation sent to a user is valid before granting access or completing registration.
Practical examples include:
- Verifying a new user's invite code during onboarding.
- Confirming invite codes in automated workflows to ensure only invited users proceed.
- Integrating invite code validation into custom user management systems.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to use. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, select "UserService". |
| userId | The unique identifier of the user whose invite code is being verified. |
| verificationCode | The invite verification code that needs to be validated for the specified user. |
Output
The node outputs a JSON object containing the response from the Zitadel API's verifyInviteCode method. This typically includes information about whether the invite code was successfully verified or if there were errors (e.g., invalid or expired code). The exact structure depends on the Zitadel API response schema for this operation.
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 credentials: Ensure the Zitadel API token is correctly set up in n8n credentials; otherwise, authorization will fail.
- Incorrect userId or verificationCode: Double-check that the user ID and invite code are correct and correspond to existing invites.
- Parsing errors: Input properties like
userIdandverificationCodeare parsed as strings; malformed JSON input may cause errors. - Operation not found: Selecting an unsupported operation for the chosen service will result in no action; verify that
verifyInviteCodeis selected underUserService.