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
resendInviteCode
AI-generatedOverview
This node integrates with the Zitadel API, allowing users to perform various operations across multiple Zitadel services. Specifically, the resendInviteCode operation under the "Default" resource triggers the resending of an invitation code to a user via the UserService. This is useful in scenarios where a user did not receive or lost their original invite email and needs a new invitation sent.
Practical examples include:
- Resending an invite code to onboard a new team member who missed the initial invite.
- Automating invite management workflows within an organization using Zitadel's identity platform.
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 to whom the invite code should be resent. Required when Service is UserService and Operation is resendInviteCode. |
Output
The node outputs a JSON object representing the response from the Zitadel API for the invoked operation. For resendInviteCode, this typically includes confirmation details about the resend action (such as status or metadata). The exact structure depends on the Zitadel API response schema for that method.
No binary data output is produced by this operation.
Example output JSON snippet:
{
"status": "success",
"message": "Invite code resent to userId xyz"
}
(Note: Actual fields depend on Zitadel API response.)
Dependencies
- Requires an API authentication token (Personal Access Token) configured in n8n credentials to authorize requests to the Zitadel API.
- Connects to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk. - Uses gRPC client libraries internally to communicate with Zitadel services.
Troubleshooting
Common issues:
- Invalid or missing API token will cause authorization failures.
- Incorrect
userIdmay result in errors indicating the user was not found. - Selecting a service-operation combination that does not support the given parameters can cause runtime errors.
Error messages:
- Authorization errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Parsing errors: Input properties expecting JSON must be valid JSON strings; otherwise, parsing will fail.
- Method not found: If the selected operation is not supported by the chosen service, verify the service and operation selections.