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, allowing users to perform various operations across multiple Zitadel services. Specifically, the verifyInviteCode operation under the "Default" resource verifies an invite code for a user by sending the user ID and verification code to the Zitadel UserService.
Common scenarios include:
- Verifying user invitation codes during onboarding or registration flows.
- Automating user validation processes in identity management systems.
- Integrating Zitadel's user verification into custom workflows for access control.
For example, you might use this node to confirm that a newly invited user has entered a valid invite code before granting them access to your application.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For verifyInviteCode, must be UserService. |
| userId | The unique identifier of the user whose invite code is being verified. |
| verificationCode | The invite or verification code to validate for the specified user. |
Output
The node outputs a JSON object containing the response from the Zitadel API's verifyInviteCode method. This typically includes details about the verification result, such as success status or error information.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"verified": true,
"userId": "string",
"message": "Verification successful"
}
(Note: Actual fields depend on Zitadel's API response schema.)
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 expired verification code: The API may return an error if the code is incorrect or expired. Ensure the code is correct and still valid.
- Missing or incorrect userId: Verification will fail if the user ID does not exist or is malformed.
- Authentication errors: If the API token is missing or invalid, the node will fail to authenticate. Verify that the API key credential is correctly set up.
- JSON parsing errors: Input properties are parsed as JSON if possible; ensure string inputs like
userIdandverificationCodeare properly formatted strings without extra quotes or invalid characters. - Operation not found: If the selected operation is not supported by the chosen service, the node returns empty output. Confirm that
verifyInviteCodeis used only withUserService.