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
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 providing their user ID and the verification code. This is useful in workflows where you need to confirm that a user's invitation or registration code is valid before proceeding with further automation steps.
Practical examples include:
- Automating user onboarding by verifying invite codes automatically.
- Validating invite codes during user registration processes.
- Integrating invite code verification into custom approval or access control workflows.
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 whose invite code is being verified. Required when Service is UserService and Operation is verifyInviteCode. |
| verificationCode | The invite or verification code string that needs to be validated for the specified user. Required when Service is UserService and Operation is verifyInviteCode. |
Output
The output JSON contains the response from the Zitadel API's verifyInviteCode method. It typically includes details about the verification result, such as whether the invite code was valid or not, and any related metadata returned by the API.
If the node is called with other operations or services, the output will reflect the respective API response structure.
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 API token: Ensure the Zitadel API token credential is correctly set up in n8n; otherwise, authentication will fail.
- Incorrect userId or verificationCode: Double-check that the user ID and verification code are correct and correspond to existing records in Zitadel.
- Operation not found: If the selected operation does not exist in the chosen service, the node returns an empty JSON object.
- JSON parsing errors: Input parameters are parsed as JSON if possible; malformed JSON strings can cause errors. Provide plain strings for simple fields like userId and verificationCode.
- Network issues: Verify connectivity to the Zitadel API endpoint and ensure no firewall or proxy blocks the requests.